Telegram RegisterThe public register of Telegram

Channel

Deutsche Bahn Dilemma

@BahnDilemma

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

104subscribers

+2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001906156790
TypeChannel
Username@BahnDilemma
CreatedBetween 1 March 2023 and 30 November 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/BahnDilemma

Growth

1021041037 August 2026 — 102 subscribers9 August 2026 — 102 subscribers15 August 2026 — 104 subscribers7 August 202615 August 2026
3 measurements spanning 8 days, net +2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 102–104 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 00:44104+2
9 Aug 2026, 10:02102no change
7 Aug 2026, 11:08102first reading

Engagement

18 posts held, back to 15 March 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 27 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
3m 15s
Average length
39s

Measured directly from 5 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

83 reactions across 18 posts, in 12 distinct kinds. The most used accounts for 39.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁3339.8%
🔥1012.0%
🤣1012.0%
👍78.43%
🤮56.02%
44.82%
🤡44.82%
🙈33.61%
🤬33.61%
🥴22.41%
😍11.20%
🤨11.20%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 18 of the 18 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 83reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 15 March 2025 to 27 June 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

4 May 2026, 07:06 UTC231 views1 reactionsread 9 August 2026
Forwarded from @BeatrixvStorchPhoto

Deutsche Bahn. Next Level: Durchsage 👈warnt vor fehlerhaften Durchsagen☝️. Und Anzeigetafeln warnen vor fehlerhaften Anzeigetafeln. Man möge die Anzeige am eingefahrenen Zug kontrollieren. Das ist jetzt dann aber auch wirklich nicht mehr zu toppen. Die Bahn Sinnbild für die Bundesrepublik: kaputt.

1

22 Sept 2025, 06:44 UTC412 views7 reactionsread 9 August 2026
Photo

Die Eilmeldung des Tages: Zugausfälle und massive Verspätungen bei der extrem bunten Bahn. Also alles wie immer!🌈🌈🌈🌈 @MarcoKurz

🤬3🤣2👍1😁1

Showing the 12 most recent of 18 posts we hold for @BahnDilemma. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 15 August 2026 — this entry's latest reading, not the date you are reading this.

“Deutsche Bahn Dilemma” (@BahnDilemma), 104 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/BahnDilemma.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.