Telegram RegisterThe public register of Telegram
Telegram profile photo for Sebastian Ross

Channel

Sebastian Ross

@sebastianross

On this record: Topic · Growth · Engagement · Posts · Cite this entry

523subscribers

-29 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-1001556867223
TypeChannel
Username@sebastianross
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/sebastianross

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 97% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

523552537.57 August 2026 — 552 subscribers7 August 2026 — 552 subscribers14 August 2026 — 548 subscribers28 August 2026 — 542 subscribers6 September 2026 — 535 subscribers13 September 2026 — 533 subscribers27 September 2026 — 528 subscribers7 October 2026 — 523 subscribers7 August 20267 October 2026
8 measurements spanning 61 days, net -29. 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 519–556 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 00:17523-5
27 Sept 2026, 00:59528-5
13 Sept 2026, 13:20533-2
6 Sept 2026, 02:55535-7
28 Aug 2026, 04:23542-6
14 Aug 2026, 05:37548-4
7 Aug 2026, 01:31552no change
7 Aug 2026, 01:21552first reading

Engagement

20 posts held, back to 11 June 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 20 posts for this entry, the most recent from 13 October 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

27 Sept 2023, 09:56 UTC≈1,190 viewsread 7 August 2026

W sobotę spotykamy się w Luc Cafe w Manchester. Będzie ktoś? 5pm

Showing the 12 most recent of 20 posts we hold for @sebastianross. 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.

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 7 October 2026 — this entry's latest reading, not the date you are reading this.

“Sebastian Ross” (@sebastianross), 523 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/sebastianross.

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.