Moscow Escort by District

Moscow has been administratively split into 12 okrugs since 1991. The split is not uniform or geometric: the districts differ by a factor of ten in area, by a factor of eight in population, by orders of magnitude in business-infrastructure density. The Escort MSK catalog is organised by these 12 districts because, for matching a companion, what matters is not "Moscow in general" but the specific outbound district.

Why geography is more than a filter. A companion based around Aeroport (SAO) and a companion in Kuzminki (YUVAO) are different time plans for an evening in the City: the first reaches it in 25 minutes, the second in 50–70. For a business dinner at Sky Lounge MSU (YUZAO) the sensible matching pool is in nearby districts: CAO, ZAO, YUZAO. For a corporate event in Sokolniki (VAO) — VAO, CAO, SVAO.

What we settled in the first months. Initially we tried a single shared "Moscow" pool with district as an optional filter. It worked poorly: the manager spent 10–15 minutes per request on logistics alignment, and the client sometimes learned about a two-hour drive only after booking confirmation. After we switched to district pre-filtering, the booking-confirmation time dropped to 5–7 minutes. The "by district" page in the catalog now is not a cosmetic section — it is the main matching route for experienced clients.

Districts with a clear specialisation:

• CAO — restaurants and hotels for business dinners and social outings. The base district.
• ZAO — Moscow City, tower offices, business-register corporate events.
• SVAO — VDNKh exhibitions, media format.
• VAO — Sokolniki Expo, the Izmailovo hotel cluster.
• SAO — the Leningradsky business corridor, Sheremetyevo logistics.
• YUZAO — academic register, MSU, Sky Lounge.
• YUAO — estate-tourism, cultural programme.
• YUVAO, SZAO, ZelAO, New Moscow, TAO — niche formats with their own specialisations (see the dedicated pages).

About 70% of Moscow's business-calendar events — dinners, presentations, social outings — are concentrated in the Central Administrative District. The other 30% is spread across 11 districts with a clear specialisation each.

The business core in CAO. Inside the Boulevard Ring, on Tverskaya, in Zamoskvorechye, around Patriarch Ponds — six pedestrian clusters of restaurants and business-register hotels. Within walking distance: Four Seasons, Metropol, Ararat Park Hyatt, Ritz-Carlton, Lotte. This is where a business dinner with a foreign guest goes by default.

Tower Moscow in ZAO. Moscow City is a vertical 2010s office cluster — Federation, OKO, Empire, IQ-Quarter. Business life here runs "bottom up" — from the office on the 40th floor to Sixty on the 60th. This scenario does not repeat in any other district.

Exhibition anchors on the periphery. VDNKh in SVAO, Sokolniki Expo in VAO, Crocus Expo in Krasnogorsk (formally the region but served from Moscow) — three anchor venues of industry expos. The business scenario here is shorter: one or two days around a specific event, then the guest leaves.

The Skolkovo innograd in ZAO. An R&D cluster in the west of the capital with its own business loop. Bookings out of Skolkovo are usually a 2–3 day business-trip format tied to a specific resident meeting.

Museum Moscow in the south. Kolomenskoye and Tsaritsyno in YUAO are flagship tourist routes for a guest who flew in "to see Moscow". This is not a business register but a cultural one.

What this means for matching. If your event is in the City, a CAO or ZAO profile reaches it in 15–25 minutes. A Zelenograd profile — in two hours. That is not "better or worse", it is logistics. On each district page there are concrete routes, restaurants and peak hours — it is worth opening the relevant page before booking, to align with the manager not on "Moscow in general" but on the specific scenario.

Logistics in Moscow is half the outcome. The roads work unevenly, each district has its own rush hour, parking at the key restaurants is its own scenario. What we agree with the client before confirming the booking:

Meeting point. A hotel lobby, restaurant, airport or exhibition centre — a public place with a clear landmark. The manager fixes it in the chat one day before the event. There is no "meet me somewhere nearby" on the day.

Companion arrival time. 10–15 minutes before the event starts. For remote districts (Zelenograd, Troitsk) and difficult weather — 30 minutes.

Transfer route. When the event is in one district and then a move to another (for example, a CAO dinner → a Moscow City cocktail), that is two stages, and the manager arranges a single transport for both or two separate points. For routes with several transfers, the driver-companion format already has the logistics built in.

Venue dress code. Across the same district, dress codes differ. Turandot and Pushkin in CAO expect a jacket; Patriarch Bistro is more relaxed. Moscow City tower corporate events often run black tie — that is agreed separately 2–3 days ahead.

Common client mistakes the manager corrects at the dialogue stage:

• Not budgeting for rush-hour traffic. Thursday-Friday 19:00 in CAO is dense traffic; a 25–35 minute buffer is mandatory. For a 19:30 dinner the companion should leave by 18:00.
• Setting the meeting on "Tverskaya" without specifying the address. Tverskaya is two kilometres long; a specific address or landmark (metro station, the concrete restaurant) is fixed in advance.
• Asking for a Zelenograd companion for an evening in the City with an hour's notice. Technically that is a two-hour drive; a realistic lead time is three hours minimum, and better — match a profile that is based closer.
• Not stating the terminal at Sheremetyevo or Vnukovo. Terminals differ; the drive to the meeting point varies by up to 20 minutes.

There is no magic here: logistics aligned in advance means the event runs smoothly. Logistics left "to chance" means the event runs tense.

Half of Moscow's business events do not fit a single district. A typical scenario is a Moscow City lunch, a presentation at a gallery on Tverskoy Boulevard, a dinner at Patriarch Ponds. Three districts in one day: ZAO → CAO → CAO. What changes in the booking:

Base rule: one companion per day, not three. Swapping companions by district is a bad scenario both for logistics (a new introduction every two hours) and for the event register. One profile is matched, one that handles all three points. That is why the catalog filter works on the companion's home district, not the event district: a CAO-based companion reaches the City and back without issue.

Lead time for multi-district events. At least 48 hours for matching. For complex routes (centre → Zelenograd → centre) — 3–5 working days. This is driven by dress code: a Skolkovo corporate event and a Patriarch Ponds dinner have different outfit registers, the companion must be able to change in between (the hotel, the client's office, an agreed zone).

Routes we book regularly:

• ZAO → CAO → CAO. Lunch in the City, presentation on Tverskoy, dinner at Patriarch Ponds.
• SAO → CAO → CAO. The guest landed at Sheremetyevo, checked into the Aeroport district, evening dinner downtown.
• CAO → VAO. Daytime programme in the centre, evening corporate event in Sokolniki or Izmailovo.
• ZAO → ZAO (Moscow City → Skolkovo). A tower meeting, then an R&D visit at Skolkovo.
• CAO → YUAO. Business in the centre in the morning, a Kolomenskoye or Tsaritsyno tour after lunch.

What we do not do:

• We do not book a companion across three different parts of Moscow and the region in one day. That is no longer companionship but "a taxi with a partner". A reasonable cap is two Moscow districts per day plus one region point.
• We do not fragment the schedule into a "brief appearance in one place and a long part in another". If the main-location event is shorter than 90 minutes, a presentation format works better than a diluted companionship.

The manager, at the dialogue stage, will propose a realistic route layout if the initial brief shows too dense a programme for a single day.