RegioJet · Fare Bucket

Standard class · RJ 1021 · Warszawa → Krakow · Departs 06:00 Friday Apr 17

Data collected via RegioJet Public API · Last updated: Apr 10, 2026 05:02 UTC
Current price
29 PLN
1st class available from 59 PLN
Unchanged 14d
Seats available
47 / 75
63% free · 28 sold
Selling slowly
Observed since
Feb 16
2026 · 138 data points
High confidence

Price history — last 30 days

Standard class ticket price (PLN), RJ 1021, departure Apr 17

Seat availability — last 14 days

Available seats (of 75 total), Standard class

Events & observations

Mar 28
Price held at 29 PLN despite RegioJet exit announcement from Warsaw-Krakow corridor. No yield management response observed.
Mar 15
Seat inventory expanded from 63 to 75 — likely class reconfiguration or additional car added to consist.
Mar 10–13
Price dipped to 19 PLN for 3 days (promo window), then returned to 29 PLN. 6 additional seats sold during that window.

This view adopts Wiremind CAYZN’s ‘drill-down as default navigation’ pattern — arguably the UX signature that differentiates CAYZN from competitors like PROS and Revenue Analytics.

Wiremind CAYZN patterns adopted

  • 4-level hierarchy: Network → Corridor → Train → Fare Bucket. CAYZN uses Network → Departure → Fare Bucket; we add ‘Corridor’ since Polish rail thinks in corridors (Warszawa-Krakow, etc.).
  • Breadcrumb always visible — the analyst never loses context about where they are in the hierarchy.
  • No SQL, no report builder — every question answerable by clicking, not querying.
  • Zoom-in without losing the zoom-out context — CAYZN’s ‘ghost preview’ pattern: all four levels visible simultaneously in the navigation map.

Why this matters for our project

Our current dashboards present fixed views. Analysts cannot navigate from ‘show me the network’ to ‘show me this specific fare bucket for this specific train on this specific date’ without switching screens. CAYZN’s drill-down pattern gives analysts one unified navigation model across all depths of analysis.

“Made by revenue managers for revenue managers.” — Wiremind on CAYZN. The drill-down pattern emerged because RM analysts need to zoom in and out constantly — never leave a context, just focus deeper.

What we adapt

CAYZN’s Network → Fare Bucket is a 3-level drill-down (they think in ‘departure’ as the mid-level unit). We add Corridor because Polish rail’s commercial connections are structured around city-pair corridors. Adding Corridor as an intermediate level fits how our analysts think about the business: they ask “what’s happening on Warszawa-Krakow?” before asking “what’s happening on RJ 1021?”

Source: Wiremind CAYZN product page (wiremind.io/passenger/cayzn); Flair Airlines case study mentioning CAYZN’s ‘intuitive drill-down’ as the primary UX innovation.

What analysts find here

Level 1 — Network
Is the business healthy overall?
KPIs, alert flags, corridor summary.
Level 2 — Corridor
Where is competition intensifying?
Carrier comparison, price floor trends, occupancy heatmap.
Level 3 — Train
Is this specific service performing?
All fare buckets, booking curve position, capacity changes.
Level 4 — Fare Bucket
What’s the pricing and availability story?
Price history, seat depletion, events, yield signals.
Drill-down in action. You can reach any fare bucket from any starting point. No report builder, no SQL — just click through the breadcrumb or the navigation map below the charts.

Quick context Carrier: RegioJet
Route: Warszawa → Krakow
Train: RJ 1021
Departure: 06:00 Fri Apr 17
Class: Standard (Economy)
Booking horizon: 7 days out