> For the complete documentation index, see [llms.txt](https://docs.wingbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wingbits.com/general-help/stations/delete-a-station.md).

# Delete a station or reservation

{% hint style="warning" %}
Don't delete a station that has an extended reservation or is still onboarding. Deleting releases the location, so someone else can reserve it.
{% endhint %}

1. Go to the [My Stations](https://wingbits.com/dashboard/stations) page.
2. Click the 3 dots on the far right of the station (or reservation) and click "Delete".
3. Check the name in the confirmation, then click "Delete".

You will see "Station deleted!" (or "Reservation deleted!"). This cannot be undone.

What happens to the station:

* The device is unlinked from your account and any host is removed.
* You keep its rewards. Unclaimed rewards stay claimable, and its history still shows on the [Overview](https://wingbits.com/dashboard) page chart.

Replacing hardware or selling a station? Follow [Station Replacement](https://docs.wingbits.com/general-help/stations/station-replacement.md) or [Station Transfers](https://docs.wingbits.com/general-help/stations/station-transfers.md) so you don't lose your location.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.wingbits.com/general-help/stations/delete-a-station.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
