Can Bumble Show an Old Location?
Updated September 2026 · Reading time: 24 min
In short: Yes, and more often than most people assume. The distance printed on a Bumble card is computed from the last location the platform stored for each of the two people involved. That stored point refreshes when the app is used with location permission granted, not continuously. If the other person has not opened the app in a while, has background access restricted, uses approximate location, or has a Travel pin parked somewhere, the figure you see can describe where they were rather than where they are. On top of that, any city someone typed into their profile is frozen text that GPS never touches. An old location is not a bug. It is the normal side effect of a system designed for matching, not for tracking.
People usually land on this question for one of three reasons. Their own deck is stuck in a city they left. A match's distance looks impossible given what they know. Or a partner's profile appears to be "in" a city the partner says they have not visited in months. Each scenario has a different explanation, and the most useful thing this guide can do is help you tell them apart without over-reading a single number.
This article focuses on staleness: when, how and why an outdated location can be displayed. If you want the mechanics of refresh itself, does Bumble update location automatically covers them. If you are trying to work out whether a location means someone is currently using the app, does Bumble location mean someone is active handles that separate question. And if you want to find people in a particular city, can you search Bumble by location explains what is and is not possible.
The short answer, broken into layers
"Location" on a dating card is not one thing. It is at least four different signals that happen to share a word, and each one ages at its own speed.
| Layer | Source | Can it be old? | Typical cause of staleness |
|---|---|---|---|
| Stored search point | Device GPS at last refresh | Yes, often | Infrequent app use, restricted background access |
| Distance figure on a card | Derived from two stored points | Yes | Either side's point is old, or the card was cached |
| Travel pin | Chosen manually, usually paid | Yes, by design | Deliberately detached from the phone |
| Typed city or prompt | Written by the member | Yes, indefinitely | Never edited after a move |
When someone says "Bumble showed an old location", they almost always mean one of these four. The fix, and the interpretation, depend entirely on which.
Why the layers matter
A stored point that is two days old and a typed city that is two years old are both "old locations", but they tell you completely different things. The first suggests the person has not opened the app from a new place recently. The second tells you only that they have not bothered to edit their bio. Treating them as the same kind of evidence is the most common reasoning error in this topic.
How a location becomes stale in the first place
To understand why an old figure appears, it helps to picture the pipeline from a phone to a card on someone else's screen.
Step one: the phone reports a position
When the app is opened with location permission, the operating system hands over a position. With precise location enabled, that position is reasonably tight. With approximate location, it is deliberately fuzzed to a wider area. With permission denied, there may be nothing new at all.
Step two: the platform stores a point
The platform keeps a point it uses for matching. Think of it as an anchor. The anchor is updated when a fresh position arrives, and otherwise it simply stays where it was. Nothing about the anchor decays or expires visibly; an anchor from last Tuesday looks identical to one from five minutes ago.
Step three: the distance is calculated
When your deck is built, the platform measures the gap between your anchor and each candidate's anchor, converts it to your unit preference, and rounds it. The result is the figure printed on the card.
Step four: the card is shown, sometimes later
Decks are assembled in batches. A card can be prepared, held, and displayed a little later, and some interface elements recalculate at render while others may not. The gap between calculation and display adds another small layer of possible staleness.
Where the age accumulates
| Pipeline stage | What can make it old |
|---|---|
| Phone position | Airplane mode, weak signal, approximate-only permission |
| Stored anchor | Person has not foregrounded the app since moving |
| Distance calculation | Uses whichever anchors exist at that moment |
| Card display | Deck prepared earlier than it is viewed |
Every stage can only ever be as fresh as the one before it. A perfectly current calculation built on a four-day-old anchor produces a perfectly current-looking number that is four days out of date.
Seven concrete ways an old location reaches your screen
These are the mechanisms that actually produce outdated distances and cities. Most real cases involve one or two of them at once.
1. The other person has not opened the app since moving
This is the dominant cause. Someone visits a city, uses the app there, flies home, and does not open it again for a week. Their anchor is still in the city they visited. Anyone whose deck includes them sees a distance computed from that old point. Nothing is wrong; the system simply has no newer information.
2. Background location is restricted
Many people grant location "while using the app" only. That is a sensible privacy choice, and it means the anchor cannot move unless the app is in the foreground. Pocket the phone, cross three cities, and the anchor stays wherever the last session happened.
3. Battery optimisation froze the app
Some Android manufacturers apply aggressive power management that suspends apps a user has not opened recently. Even with generous permissions, the practical effect is the same as restricted background access: the anchor waits for the next real session.
4. A Travel pin is active or recently expired
Where a paid travel feature exists, it places the browsing area over a chosen metro for a limited window. During that window, the distance other people see reflects the pin, not the phone. When the pin expires, the anchor snaps back to the device on the next refresh. Both the pinned period and the snap-back look like "wrong" or "old" locations from the outside.
5. Approximate location blurs the point
With the precise toggle switched off, the operating system provides an area rather than a point. The anchor becomes coarse, and distance figures stop moving for small changes. A person who moves across town may produce no visible change at all, which reads as a location stuck in the past.
6. Your own anchor is the stale one
Distance is a subtraction with two sides. If your anchor is old, every card in your deck is measured from the wrong starting point. People often assume the other person's location is outdated when the lag is actually on their own phone.
7. The typed city was never updated
Profile text, prompts and any written "lives in" style field are authored by the member. They reflect whatever was true, or aspirational, when they were written. A person who moved from Manchester to Leeds three years ago may still have Manchester in a prompt, and no refresh will ever change that.
Summary of the seven
| Mechanism | Whose side | How old it can get | Visible clue |
|---|---|---|---|
| No app use since moving | Theirs | Days to weeks | Distance inconsistent with what they told you |
| Foreground-only permission | Theirs or yours | Until next session | Figure updates only after they open the app |
| Battery optimisation | Theirs or yours | Until next session | Similar to above, device-dependent |
| Travel pin | Theirs or yours | Duration of the pin | Very large, sudden jumps |
| Approximate location | Theirs or yours | Indefinite blur | Figure oddly stable despite movement |
| Your own stale anchor | Yours | Until your next session | Whole deck feels shifted |
| Unedited typed city | Theirs | Years | Text and distance disagree |
Travel Mode: the deliberate old-or-wrong location
Travel features deserve their own section because they produce the most dramatic mismatches, and because people frequently misread them as evidence of something.
What a Travel pin does
A Travel-style feature lets a member place their browsing area in a different city for a set period, commonly a few days, with the exact duration and pricing depending on plan and market. During that window the platform treats them as located at the pin for matching purposes. People in the pinned city can see them as nearby, and they see people from that city.
How it creates an "old" location
Consider someone who sets a pin over Lisbon before a holiday, then cancels the trip. For the rest of the window, their distance from anyone in Lisbon looks small, even though their phone never left home. When the window closes and they next open the app, the anchor returns to their device. Anyone who saw them as "two miles away" in Lisbon is now looking at a location that was never physically real.
The reverse also happens. Someone genuinely travels, uses a pin in advance, and their distance shows the destination before they arrive. From the outside, the location looks as if it jumped early.
Why you cannot tell from the card
| What you see | Possible reality |
|---|---|
| Small distance in your city | They are here, or they pinned your city, or their anchor is from a past visit |
| Large distance from their home city | They travelled, or they pinned elsewhere, or your anchor is old |
| Sudden jump of hundreds of miles | Travel pin switched on or off, or a real flight followed by a session |
The interface does not label Travel pins on other people's cards in a way that lets you audit them. You receive one rounded number and no provenance.
Travel pin versus stale anchor
| Property | Stale anchor | Travel pin |
|---|---|---|
| Chosen deliberately | No | Yes |
| Tied to past physical presence | Yes | Not necessarily |
| Ends by itself | When the person next opens the app | When the window expires |
| Usually paid | No | Usually |
| Evidence of being somewhere | Weak, and outdated | None |
Both produce locations that do not match the present. Only one of them ever reflected a real position, and even that one is past tense.
The typed city problem
The written layer causes more confusion than any GPS behaviour, because it looks so authoritative.
Authored text never refreshes
Anything a member types, whether a city in a profile field, a neighbourhood in a prompt, or a line like "new to Berlin", stays exactly as written until they edit it. There is no mechanism that compares typed text to device location and corrects it.
Common mismatches
- A profile says one city, the distance points to another two hundred miles away.
- A prompt says "just moved here", and the profile has clearly been live for years.
- A bio names a university town the person graduated from long ago.
- A hometown field is read as a current city.
Each of these is a person describing themselves at some point in time, in their own words. None of them is a location reading.
How to weigh typed text against distance
| Signal | What it tells you | How much weight to give it |
|---|---|---|
| Typed city | What the person chose to say, at some point | Low for current location, useful as a descriptive clue |
| Distance figure | Gap between two stored anchors, rounded | Moderate for rough proximity, low for timing |
| Both agree | Consistent story, still not proof of presence | Somewhat higher, still approximate |
| Both disagree | Normal, usually mundane | Do not treat as a contradiction to resolve |
The honest reading of a disagreement is almost always "one of these layers is older than the other". Usually the typed text is the older one.
Is it stale, or is it just rounding?
Not every odd-looking figure is old. Some are simply blunt.
Rounding bands hide movement
Distances are rounded into bands. At short range, a small move may not cross a band boundary, so the figure stays still. At longer range, bands are wider still. A figure that has not changed in days might be current and simply insensitive to the movement that happened.
Rounding can also create fake movement
When a true distance sits near a band edge, tiny recalculations flip the displayed value back and forth. That looks like movement without any movement on the ground. It can also look like a return to an "old" value, when really the number is oscillating around a boundary.
A quick diagnostic
| Pattern | Most likely explanation |
|---|---|
| Figure identical for days, person says they travelled | Stale anchor or approximate location |
| Figure flickers between two adjacent values | Rounding boundary |
| Figure jumps hundreds of miles and back | Travel pin on and off |
| Every card in your deck shifts at once | Your own anchor refreshed |
| Figure contradicts typed city | Typed text is older than the anchor |
This table is a starting point for reasoning, not a verdict. The interface does not provide enough information for any single pattern to be conclusive.
When your own location is the old one
Many readers are asking about their own profile rather than someone else's. The symptoms of a stale personal anchor are distinctive.
Symptoms
- The deck keeps serving people from the city you left.
- Matches say you look close when you are obviously far away.
- Your radius filter produces results that make sense only from your old address.
- Someone in your new city tells you your card shows a large distance.
Why it happens
Your anchor refreshes on real sessions with permission granted. If you moved but have only opened the app briefly, or if the app is set to foreground-only access and battery optimisation suspends it, the anchor may lag. A Travel pin you forgot about can outrank everything until it expires.
How to fix it
- Check location permission. Make sure the app is allowed to access location, and enable precise location if you want tight distances.
- Look for an active travel override. If you set one before a trip, it may still be running.
- Open the app where you now are. Let a full deck load rather than opening and closing immediately.
- Review battery settings. Exempt the app from aggressive power saving if your device applies it.
- Edit your typed city. Change any prompt or field that names the old place; no GPS refresh will do it for you.
- Give it a session or two. Decks are built in batches, so the first new deck may still include cards prepared from the older anchor.
- Reinstall only as a last step. Reinstalling mostly resets permission prompts you could have fixed directly.
What others will see after the fix
Once your anchor refreshes, other members see distances computed from the new point the next time their deck includes you. They do not receive a notification, a "moved" badge, or a trail. Your card simply starts showing a different number.
When someone else's location looks old
This is where most of the anxiety lives. You see a distance or a city and it does not fit what you know.
The four honest possibilities
- Their anchor is old. They have not opened the app since being somewhere else.
- Your anchor is old. The mismatch is on your side.
- A Travel pin is involved. On either side.
- The typed layer is old. The text was written long ago.
There is a fifth possibility people tend to jump to first, which is that the figure reveals something hidden. It is the least supported by the data. The figure is rounded, possibly stale, and possibly pinned. It cannot carry the weight of a hidden story.
Questions a stale figure cannot answer
| Question | Why the figure cannot answer it |
|---|---|
| Where are they now? | The anchor may be days old |
| When were they last there? | No timestamp is displayed |
| Are they using the app? | Location and activity come from different systems |
| Did they travel with someone? | Nothing in the figure relates to other people |
| Are they lying about their city? | Typed text and anchors age independently |
If the real question is activity rather than geography, how to tell if a Bumble profile is active and does Bumble show inactive profiles cover the visibility side. For how long dormant accounts linger, how long Bumble shows inactive profiles goes further.
Old location versus inactive profile
These two ideas are tangled together so often that they deserve direct separation.
Why people link them
A figure that has not moved in weeks feels like a sign of abandonment. Sometimes it is. But the same frozen figure is equally consistent with someone who uses the app daily from the same neighbourhood, someone with approximate location enabled, or someone who opens the app only at home.
Why they are different systems
Activity is about sessions: whether and when someone opens the app, swipes, or messages. Location is about anchors: where the platform last placed them. A person can be highly active with an unchanging anchor, and completely inactive with an anchor that was fresh the last time they used the app.
| Situation | Anchor | Activity |
|---|---|---|
| Daily user, same neighbourhood | Stable, current | High |
| Daily user, approximate location | Stable, blurred | High |
| Occasional user who travelled | Old, from the trip | Low |
| Former user, account left open | Old, from the last session | None |
| Snoozed profile | Unchanged, not shown | Paused |
A stale location is weak evidence of anything about activity. The dedicated explainer on whether Bumble location means someone is active goes deeper into why.
Snooze, Incognito and deleted accounts
Visibility controls interact with staleness in ways that surprise people.
Snooze
A snoozed profile is paused from appearing. Its anchor does not move while snoozed if the person is not using the app. When they return, the first refresh may shift the figure noticeably, which looks as if they "moved" during the pause. In reality, the anchor simply caught up.
Incognito
Incognito limits who sees a profile, typically to people the member has already liked. It does not freeze or reveal location. But because the profile appears to fewer people, any given viewer sees it less often, and the distance they remember may be older than they think.
Deleted or abandoned accounts
A deleted account should stop appearing. An abandoned but undeleted account may continue to exist with an anchor from its final session. If it ever surfaces, its distance reflects that last session, which could be months ago.
| Control | Effect on anchor | Effect on what you see |
|---|---|---|
| Snooze | No movement while unused | Profile hidden, then possible jump on return |
| Incognito | Normal refresh when used | Seen by fewer people, less often |
| Deleted | Removed | Profile should no longer appear |
| Abandoned | Frozen at last session | Old distance if it surfaces |
Can you search by an old city?
Some readers want to use a previous city as a search key, hoping to find a profile that was once set there.
What the app offers
Discovery is built around your anchor, your radius and your filters. There is no directory where you type a city and a name and receive a list. A Travel pin lets you browse another metro, but that is sampling a ranked deck, not searching.
Why old cities make this harder
If someone's anchor has moved since, they will not appear in a deck built around the old city, regardless of what their typed text says. If their anchor is stale and still sits in the old city, they might appear, but only if they also pass every filter and ranking rule. Neither case gives you a reliable method.
The broader limits are covered in can you search Bumble by location, and the remote-city scenario is handled in find someone on Bumble in another city.
Real situations, read carefully
"My deck is still full of people from my old city"
Your anchor has not refreshed, or a Travel pin is still active. Run through the fix list above: permission, precise toggle, travel override, battery settings, a full session in the new location. Expect the lag to clear within a session or two of real use.
"A match says they live near me but their card says 300 miles"
Their anchor may be from a trip, or yours may be. Alternatively, they may have a pin active elsewhere. Ask them. The answer is almost always mundane, and asking is faster than theorising.
"My partner's profile shows them in a city they say they left"
Three explanations are more likely than any dramatic one: their anchor is from the last time they opened the app, their typed text is old, or the profile is an abandoned account they never deleted. None of these tells you when the profile was last used. If the concern is about the relationship, the number will not resolve it. A calm conversation is the tool that actually works. For a broader, measured approach, how to know if a partner is on Bumble sets out what can and cannot be concluded.
"The distance jumped from 5 miles to 400 overnight"
That size of jump points strongly to a Travel pin switching on or off, or to a real journey followed by a session. It does not indicate anything about who they were with or why.
"The distance has been the same for weeks"
Either the person uses the app from the same area, uses approximate location, or has not opened the app. The figure alone cannot tell you which.
"Someone saw me as nearby in a city I visited last month"
Your own anchor was stale. You have not opened the app with location allowed since returning, or a pin was left running. Open the app at home and let it refresh.
Myths about old locations
Myth: if a distance is shown, it is current. A distance is computed from stored anchors, which can be days or weeks old. The display looks equally confident either way.
Myth: a stale location proves someone is hiding where they are. Most stale locations come from infrequent app use or restrictive permissions, not concealment.
Myth: the app keeps a location history other people can see. Members see a single rounded figure. There is no timeline and no map.
Myth: Travel Mode shows where someone really went. A pin shows where someone chose to browse. It can be set without ever travelling.
Myth: an old typed city means the person is lying. Most people never edit a bio after moving. Old text is ordinary.
Myth: if the distance does not change, the person is inactive. Stable figures come just as easily from daily use in one area or from approximate location.
Myth: refreshing your own app updates everyone else's location. You can only refresh your own anchor. Other people's anchors update when they use the app.
Myth: someone can unlock a person's "real" current location with a paid tool. No legitimate service can read live coordinates from a mainstream dating platform. Products claiming otherwise are scams, spoofing tools or malware.
Ethics: why old locations should stay uninteresting
Stale location data is tempting precisely because it feels like a clue. It is worth being clear about where curiosity turns into something harmful.
Reading a figure on a card you were shown is ordinary use. Building a record of someone's figures over time to reconstruct their movements is surveillance, even when each reading felt public. Old locations make this worse, not better: they add false precision to guesses about the past.
Practical boundaries:
- Do not log a person's distance readings across days or weeks.
- Do not set Travel pins or spoof device location to monitor a specific person.
- Do not create extra accounts to observe someone who has stopped talking to you.
- Do not present a stale distance or typed city as evidence in a dispute.
- Do not buy anything sold as a way to reveal a dating app user's real location.
- Do not share screenshots of someone's profile for others to analyse.
Where there is harassment, impersonation, coercion or a safety concern, use the platform's reporting tools and local support services. Location figures, stale or fresh, are not an investigative instrument.
Which question are you really asking?
| What you want | Where to go |
|---|---|
| My own deck to stop showing my old city | Permission, precise toggle, travel override, battery settings, a full session |
| To understand one outdated distance | Remember the seven mechanisms; none is distinguishable from the card |
| To know if a location means current activity | Does Bumble location mean someone is active |
| To understand how refresh works | Does Bumble update location automatically |
| To find people in a specific city | Can you search Bumble by location |
| To tell whether a profile is dormant | How to tell if a Bumble profile is active |
| To resolve a trust question | A conversation, not a number |
Three questions before you read into a figure
Is the thing I am worried about my own settings, or someone else's behaviour? If this figure is old, what would a fresh one need to show to change my mind? And would any possible reading change a conversation I already need to have? If the honest answers are "someone else", "I do not know" and "no", the figure is not information you can use.
A different kind of search
Old anchors, rounded bands and pinned cities all share one limitation: they describe geography approximately and after the fact. They were never meant to identify a person.
An alternative approach ignores coordinates entirely and matches on the descriptive details people tend to reuse when they write a dating profile.
Trackly takes that approach. You enter a first name, an approximate age, a city, gender, orientation and, optionally, a photo. No email address or phone number is accepted as a search key. The live check runs on Tinder. Searches are private, and the person being searched for is not notified.
In this method, the city is something you supply as a clue about where a person is likely to date. It is not read from anyone's phone, and it is not a position. That difference is what separates a respectful search from a tracker.
Interpreting results
| Outcome | Sensible reading |
|---|---|
| A match in the city you entered | Worth a careful look; still not a location |
| A match listing a different city | People move, commute and describe themselves loosely |
| No match | Different name form, age band, city or orientation, or no profile |
| Several possible matches | Use the photo and age to narrow down; avoid forcing a conclusion |
Results are signals about what a profile says, not about where someone stands or what they are doing.
For the broader method and its limits across this cluster, the pillar guide to finding a profile is the place to start.
Related reading
- Pillar: Find a Bumble profile
- Refresh mechanics: Does Bumble update location automatically
- Location versus activity: Does Bumble location mean someone is active
- Search by city: Can you search Bumble by location
- Remote cities: Find someone on Bumble in another city
- Dormant profiles: How to tell if a Bumble profile is active
- Relationship concerns: Partner on Bumble: how to know
- Start a private search: /tracker/name
Location figures on dating apps are approximate, delayed and sometimes deliberately pinned elsewhere. An old location is not proof of presence, absence, travel or relationship behaviour.