Arc Raiders buried city map: what you see and how to read it
The Arc Raiders buried city map is the central reference tool for any squad planning a run into one of the game’s most vertical, ruin-heavy environments. Before you queue a match, the map tells you where streets funnel into choke points, which rooftops connect to which alleys, and where the extraction corridors tend to collapse when a third-party squad rotates in. Treating the map as a planning surface rather than a quick reference changes how you move through the raid.
Most players open the map, glance at their spawn, and rush the nearest landmark. That habit is fine for a warm-up round, but it leaves value on the table. The buried city map is dense with routing choices, several distinct elevation layers, and a handful of contested pockets where fights cluster every session. Reading it deliberately takes a few minutes per session, and the return shows up in fewer lost loadouts and more successful extractions.
Below is a practical walkthrough of how the map is structured, how to use its filters, what the route overlays actually mean, and how to plan a run that fits your squad’s pace. The guidance is grounded in the published interactive map interface, so you can verify every claim against the live tool itself.
What the buried city map actually shows
The buried city map is a top-down representation of a single large urban environment, drawn at the scale players need to plan routes rather than to admire scenery. Streets, plazas, building footprints, and the major vertical links between them are all visible. Elevation is implied through shading and connector lines, not through a full 3D view, so the trick is to learn the conventions once and then read them quickly during a planning moment.
The map is interactive rather than static. Players can pan, zoom, and toggle layers to focus on what they care about for a given run. Squad leads tend to use the full overview during pre-match planning, while individual players zoom in on a single block when they need to identify a building entrance or a stairwell connection.
Core interface elements
Getting comfortable with the default interface is the first step. The buried city map exposes a small set of controls, and each one changes the information density of the view.
- Search: a text field for jumping directly to a named landmark, district, or route node.
- Show All / Hide All: a master toggle for the overlay layers so you can strip the map back to bare streets and rebuild it one filter at a time.
- Filters: per-layer toggles for routes, heatmap, squad, found items, and similar categories.
- Draw: a tool for sketching a custom path or marking a point before you commit to a route.
- EU toggle: switches the active region or event set, since the buried city map can show different overlays depending on the live event cycle.
- Settings: controls for visual preferences such as icon size and label density.
The most useful habit is to start each planning pass with Hide All, then turn on only the layers relevant to the current objective. A loot run benefits from the found-items layer, while a contested rotation benefits more from the heatmap and squad layers. Mixing too many layers at once produces a busy view that hides the route information you actually need.
Routes layer: planning a path that survives contact
The routes layer is where the buried city map earns its keep. It highlights commonly traveled paths between landmarks and extraction points, color-coded so you can read the dominant flow at a glance. Routes are not hard-coded walkways; they are aggregated patterns that the community uses heavily, which means a popular route is also a place where third-party squads tend to set up ambushes.
When you turn on routes, three things tend to happen. First, you see the high-traffic arteries that connect spawn zones to the main loot pockets. Second, you see the secondary loops that flank those arteries, which experienced players use to avoid the central corridors. Third, you start to notice where multiple routes converge, because those intersections are the natural ambush points.
For a squad of two or three, the practical workflow is to pick one primary route, identify one flanking route, and decide in advance which one you will take if the primary path is already occupied. That decision belongs in the pre-match planning window, not in the first thirty seconds of the raid.
How to read route color and weight
Route overlays typically use both color and line weight to indicate traffic. Thicker, warmer lines represent heavily used paths; thinner, cooler lines represent quieter detours. The exact convention is set by the map provider, so spend a few minutes scrolling through the view to learn the legend before committing to a plan. The published Arc Raiders buried city map exposes this overlay directly, which is the fastest way to confirm what the current legend looks like.
Heatmap layer: where the action actually happens
The heatmap layer is a second-order signal. It does not show a route, it shows where squads tend to spend time, fight, or die. Used carefully, the heatmap tells you which buildings are worth the risk and which are already being looted by other squads the moment you arrive.
For new players, the heatmap is a learning aid: it surfaces the contested pockets without requiring you to lose a loadout to discover them. For experienced players, the heatmap is a counter-planning aid: it tells you where not to go, because entering an already-hot zone with a half-empty backpack is a fast way to lose everything.
A useful approach is to plan a route that skirts the heatmap’s hottest cells rather than cutting through them. The longer path is often faster in practice because it avoids the time spent in combat, healing, and repositioning.
Squad layer: coordinating without voice
The squad layer exposes where your teammates are on the map, assuming they have the layer active. In a coordinated group, this layer is the simplest way to keep a loose formation without constant voice callouts. In a pickup group, it is a way to keep tabs on a teammate who has wandered off the planned route.
For solo players queueing with randoms, the squad layer is most useful for two specific moments: the initial push, when you need to know whether your team is committing to the same landmark, and the extraction phase, when you need to know whether your team is actually heading to the same exit. Both moments are where squads fall apart, and both are where a glance at the map can save a run.
Found items and loot planning
The found items layer is the most directly economic of the overlays. It marks where specific resources, containers, and rare drops have been recorded, which is useful for planning a loot-focused run. The layer is most valuable early in a season, when the economy is still settling and players are still mapping where the high-value nodes actually live.
A few practical notes about the found items layer:
- It is a record, not a guarantee. A marked item location means a player reported a find there, not that the item will be there on your run.
- It rewards repetition. A node that has been logged once is interesting; a node that has been logged many times is a reliable waypoint for a farming route.
- It ages. Hot patches and nerfs can move loot density between seasons, so a stale found-items layer can mislead more than it helps.
For a serious farming run, the best use of the found items layer is to identify two or three high-density nodes and plan a loop that visits them in order, then heads for extraction before any third-party squad can rotate in.
Landmarks, elevation, and verticality
The buried city is not a flat city. It has collapsed overpasses, intact mid-rise blocks, partially flooded sub-levels, and rooftop paths that connect buildings which look separate from street level. The published interactive Buried City view flattens this vertical stack into a single 2D surface, encoding elevation through landmark labels and the connector lines between them rather than through true 3D geometry.
The practical implication is that two landmarks which look adjacent on the map may require a long vertical detour in the raid. A rooftop that appears to overlook a plaza may be unreachable from the plaza without a specific interior stairwell, and a collapsed section that looks like a shortcut may actually be a dead end. The only reliable way to internalize these relationships is to spend a few sessions running the map with the routes layer off, so that you learn the terrain from direct observation rather than from the community’s preferred paths.
Key landmark categories
While the exact landmark set evolves with patches, the buried city map tends to organize points of interest into a few stable categories. The table below summarizes the typical roles; the live map is the source of truth for the current labels.
| Landmark type | Typical role | Planning implication |
|---|---|---|
| Central plaza or junction | Major traffic hub with high visibility | Avoid during contested rotations; useful only when you need to push a third party |
| Perimeter block | Quieter streets on the map edge | Good for cautious squads and solo extractions |
| Rooftop complex | Vertical lane with strong sightlines | Excellent for ambushes; risky if a squad holds the high ground above |
| Sub-level access | Underground corridors connecting otherwise separate blocks | Fast but enclosed; bring a close-range loadout |
| Extraction point | Final exit, often at the map edge | Pre-plan two approach routes to handle campers |
Filter presets for common run types
The filters menu is the most underused part of the buried city map. Most players leave every layer on, then complain that the map is too busy. A more productive approach is to build two or three saved views and switch between them depending on the run type, the table below shows three practical starting points.
| Preset | Routes | Heatmap | Squad | Found items | Best use |
|---|---|---|---|---|---|
| Combat view | Off | On | On | Off | Planning a push into a contested zone or rotating around a hot pocket |
| Loot view | On | Off | On | On | Farming run where you want to know what is in each building before you enter |
| Extraction view | On | On | On | Off | Final two minutes of a raid, zoomed to the map edge and any active exit |
The settings menu also lets you adjust icon size and label density, which sounds trivial but matters on smaller screens where the default icon size crowds the streets. A slightly smaller icon size and a slightly larger label can make the difference between reading a route at a glance and squinting at a cluttered block.
Pre-match planning: a 90-second routine
Most players do not need a long pre-match briefing. They need a short, repeatable routine that produces a workable plan before the raid starts. The routine below is a reasonable default; adjust it to your squad’s communication style.
- Open the buried city map and turn off every layer except routes and squad.
- Identify your likely spawn area based on the queue and note the two nearest high-traffic routes.
- Pick one primary objective: a loot pocket, a contested landmark, or an early extraction.
- Choose a primary route to the objective and a flanking route in case the primary is taken.
- Pick a tentative extraction point and identify one alternate exit.
- Close the map, confirm roles, and queue.
Ninety seconds is enough. The goal is not to plan a perfect run; it is to enter the raid with a default decision for the most common situations, so that the in-match decisions are smaller and faster.
In-match map habits
The map is also useful mid-raid, not just before it. Three habits tend to separate reliable runs from chaotic ones.
- Glance at the map after every fight. A 3-second check tells you whether the noise you just made is about to attract a third party, and which direction the third party is most likely to come from.
- Check the map before committing to a long route. If the route crosses a known heatmap hotspot, the cost of taking it is higher than the map suggests.
- Open the map during the extraction countdown. The final minute is when most raids are lost, and the map is the fastest way to confirm that your squad is actually converging on the same exit.
None of these checks take more than a few seconds, and together they convert the buried city map from a pre-match tool into a live planning surface.
Common mistakes when reading the map
Most misreads of the buried city map fall into a small set of recurring errors. The list below is not exhaustive, but it covers the patterns that show up in post-match reviews.
- Treating routes as safe paths. Popular routes are popular precisely because they are efficient, which is exactly why third-party squads set up there.
- Ignoring elevation. A 2D map hides vertical separation, and the buried city punishes players who assume rooftops and plazas are interchangeable.
- Planning only one extraction. The extraction point you wanted is often the extraction point someone else is camping. A backup exit turns a lost raid into a close call.
- Overloading the view. Turning on every layer produces a map that looks thorough but is actually harder to read than a stripped-down view.
- Skipping the pre-match routine. Entering the raid without a default plan forces every in-match decision to start from zero.
The fix for each of these is the same: a short planning pass before the raid, a small set of saved views, and a habit of glancing at the map during natural pauses in the action.
How the buried city map fits the broader raid flow
The buried city is a useful case study for thinking about how raid maps are designed in general. Other extraction-style games lean more on hand-crafted POIs, while Arc Raiders layers aggregated community data on top of the base environment to surface the routes that actually matter. That design choice is part of why the filters and heatmap layers carry so much weight: the map is not just showing you the city, it is showing you how the player base has learned to move through it. Seasonal updates tend to shift map balance, event cadence, and loot distribution, so a route that is hot one week can go quiet the next once a patch moves the contested loot nodes elsewhere.
When to trust the map, and when to trust your eyes
The buried city map is a planning tool, not a perfect oracle. The routes layer reflects what the community tends to do, not what is optimal for your squad. The heatmap reflects where fights happen, not where you will personally win them. The found-items layer reflects past reports, not guaranteed spawns.
The right balance is to use the map to set a default plan, then adapt to what you actually see in the raid. If the primary route is empty when you arrive, push it; if it is already occupied, fall back to the flanking route without argument. If the heatmap shows a hot zone but your squad has a strong composition for that fight, take the fight. The map is the starting point. Your read of the actual raid is the deciding factor.
Closing reminder: the map is a habit, not a button
Players who get the most out of the buried city map treat it as part of the loop: open it before the raid, glance at it during natural pauses, and use it to make the next decision faster. The map will not win a fight for you, but it will make sure you arrive at the right fight with the right plan, which is the difference between a frustrating run and a clean extraction.
Frequently asked questions
What is the Arc Raiders buried city map used for?
The buried city map is the planning tool for raids set in the game’s urban environment. It shows streets, landmarks, elevation hints, and several overlay layers including routes, heatmap, squad positions, and found items. Most players use it for pre-match planning and for quick in-match orientation during combat and extraction.
Where can I open the live buried city map?
The interactive map is published on a community-maintained site dedicated to Arc Raiders. It exposes the same filters, routes, and settings described here, so you can verify the current layer behavior directly rather than relying on a static screenshot.
What does the routes layer actually show?
The routes layer shows commonly used paths between landmarks, derived from aggregated player movement. Thicker lines typically indicate heavier traffic, and thinner lines indicate quieter detours. The layer is useful for identifying both fast routes and the ambush points that form along them.
Is the heatmap layer the same as the routes layer?
No. The routes layer shows where players tend to move, while the heatmap layer shows where players tend to fight, loot, or spend time. The two layers answer different planning questions, and experienced players often toggle between them rather than leaving both on at once.
How accurate is the found items layer?
The found items layer reflects reported finds rather than guaranteed spawns. A node that has been logged many times is usually reliable, while a node logged only once may have been a one-off drop, a seasonal spawn, or a player mistake. Use the layer as a hint, not a promise, and cross-check with your own observation over a few runs.
Should I plan a route before every raid?
Yes, even if the plan is simple. A 90-second pre-match routine that picks a primary route, a flanking route, and a backup extraction is enough to handle most situations. Entering a raid with no default plan forces every in-match decision to start from zero, which is how squads fall apart in the first thirty seconds.
Can the buried city map be used mid-raid?
Yes. A quick glance at the map after a fight, before committing to a long route, and during the extraction countdown is a reliable habit. Each check takes only a few seconds, and together they turn the map from a pre-match tool into a live planning surface.
Why does the map sometimes look different between sessions?
The active overlays depend on the live event cycle and the region toggle. Some layers are only populated during specific events, and the EU toggle can change which event set is active. If a layer looks empty, check the filter toggles and the event cycle before assuming the map is broken.
Does the buried city map show extraction points clearly?
Extraction points are marked on the map, and they are usually placed at the edges of the playable area. Because extraction is the most camped moment of a raid, planning two approach routes in advance is the single most useful thing you can do with the map before queuing.
How does the buried city map relate to the broader Arc Raiders design?
The map is a good case study in how Arc Raiders blends hand-crafted level design with aggregated community data. The base environment is built by the developers, but the routes, heatmap, and found-items layers are populated by how players actually move through that environment, which is why the map becomes more useful the longer a season has been live.