The published network, counted

Every figure on this page comes from one document Wizz Air publishes openly each morning, and from nothing else.

Loops in today's network

4,051

distinct loops of four flights or fewer

Counted from the 909 city pairs on today's list, which the document states is valid for 4 days. Each loop counted once, whichever city it is written from.

Today's list is valid for 4 days and names 909 city pairs. Read as a network, those pairs form 4,051 distinct ways to leave a city and come back to it in four flights or fewer.

Of those, the simplest need two flights: 132 city pairs are published in both directions today, so the document names the way out and the way back.

Visit one city and return
132
Visit two cities and return
311
Visit two cities, returning through one of them
841
Visit three cities and return
2,767

Walking from every city finds the same loop once per city on it. Deduplicated here, which is why this figure is smaller than a naive walk reports. 107 cities appear in at least one loop.

Most of the network does not bring you back

645 — 71%

of today's pairs are published in one direction only

909 pairs today, of which 132 appear in both directions. The rest are one-way: the document names the outbound and does not name the return.

The list reads like a map of places to go. 645 of today's pairs — 71% of them — are published in one direction only. Just 132 city pairs are named both ways, which is what makes coming home the harder half of planning on this pass.

The network breathes

624–938

city pairs per morning

Narrowest and widest morning across 28 recorded documents.

50%

between the quietest and busiest morning

Widest divided by narrowest, as a percentage.

28

consecutive mornings recorded

Jul 27, 2026 to Aug 23, 2026, with 0 missing days.

·0city pairs

22,515 pair observations in total, covering 1,743 distinct city pairs. Each frame is one published document — no interpolation between mornings, and no route drawn on a morning it was not published.

Furniture and weather

Named every recorded morning

  • AGP FCO (AGPFCO) 28/28
  • AHO SOF (AHOSOF) 28/28
  • ARN SKP (ARNSKP) 28/28
  • BGO GDN (BGOGDN) 28/28
  • BGO WAW (BGOWAW) 28/28

Named on only a few mornings

  • AGP WRO (AGPWRO) 2/28
  • BBU BLL (BBUBLL) 2/28
  • BBU EIN (BBUEIN) 2/28
  • BBU LPA (BBULPA) 2/28
  • BBU SVQ (BBUSVQ) 2/28

LTN–BCM left the list and returned to it 9 times in 28 mornings.

Share is the number of published mornings a pair was named on, out of the mornings recorded. Pairs seen only once are excluded from the variable column: one appearance is as likely to be a route that started yesterday as an unreliable one.

How this was measured

Wizz Air publishes one PDF each morning listing which city pairs its All You Can Fly members may book. Aloft fetches that document — without a login, without a session, without a browser — reads the pairs out of it, and stores each morning's list. Nothing here is scraped from a booking system, and nothing here reserves or books anything.

aycf-availability.pdf public, fetched without credentials

The document states its own validity window. Of 28 recorded, 24 covered four calendar days and 4 covered three.

What this document does not contain

  • No departure or arrival times. The document names city pairs, not flights.
  • No prices or fees.
  • No flight numbers.
  • No date for any individual pair — only one validity window covering the whole list, so which day a given pair flies is not stated.
  • No seat availability. A pair being published means it may be booked, not that a seat is free when you try.

So a loop on this page is a path the published network permits, not a trip anyone has confirmed can be flown in that order. Nothing here should be read as a promise of a seat.

More about Aloft