Telegram RegisterThe public register of Telegram
Telegram profile photo for QUICK LINE 247

Channel

QUICK LINE 247

@Quickline247

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

24,877subscribers

+9,623 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002377623911
TypeChannel
Username@Quickline247
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live28 October 2026
Measurements held42
Confirmed unchanged1 time, most recently 28 October 2026
On Telegramt.me/Quickline247

Topic

Sports — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.

Growth

3,99425,81314,903.57 August 2026 — 15,254 subscribers8 August 2026 — 14,703 subscribers9 August 2026 — 14,433 subscribers10 August 2026 — 13,885 subscribers11 August 2026 — 13,271 subscribers12 August 2026 — 12,865 subscribers13 August 2026 — 12,717 subscribers14 August 2026 — 12,472 subscribers16 August 2026 — 11,688 subscribers17 August 2026 — 11,088 subscribers18 August 2026 — 10,735 subscribers19 August 2026 — 10,483 subscribers20 August 2026 — 10,220 subscribers21 August 2026 — 10,153 subscribers23 August 2026 — 10,127 subscribers24 August 2026 — 10,114 subscribers25 August 2026 — 10,057 subscribers26 August 2026 — 9,799 subscribers29 August 2026 — 9,431 subscribers1 September 2026 — 8,451 subscribers5 September 2026 — 7,753 subscribers11 September 2026 — 7,056 subscribers14 September 2026 — 5,741 subscribers18 September 2026 — 4,988 subscribers27 September 2026 — 4,357 subscribers5 October 2026 — 3,994 subscribers12 October 2026 — 25,813 subscribers14 October 2026 — 25,609 subscribers15 October 2026 — 25,477 subscribers16 October 2026 — 25,408 subscribers17 October 2026 — 25,356 subscribers18 October 2026 — 25,332 subscribers19 October 2026 — 25,299 subscribers20 October 2026 — 25,247 subscribers21 October 2026 — 25,225 subscribers22 October 2026 — 25,157 subscribers23 October 2026 — 25,127 subscribers24 October 2026 — 25,049 subscribers25 October 2026 — 25,015 subscribers26 October 2026 — 24,975 subscribers27 October 2026 — 24,952 subscribers28 October 2026 — 24,877 subscribers24,8777 August 202628 October 2026
42 measurements spanning 82 days, net +9,623. 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 721–29,086 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 42
Measured (UTC)SubscribersChange
28 Oct 2026, 21:1724,877-75
27 Oct 2026, 18:1024,952-23
26 Oct 2026, 20:0524,975-40
25 Oct 2026, 22:3825,015-34
24 Oct 2026, 21:3725,049-78
23 Oct 2026, 18:5525,127-30
22 Oct 2026, 22:0825,157-68
21 Oct 2026, 16:3725,225-22
20 Oct 2026, 10:1125,247-52
19 Oct 2026, 08:3925,299-33
18 Oct 2026, 08:0025,332-24
17 Oct 2026, 09:1925,356-52
16 Oct 2026, 10:2725,408-69
15 Oct 2026, 10:0625,477-132
14 Oct 2026, 07:1925,609-204
12 Oct 2026, 13:3925,813+21,819
5 Oct 2026, 15:363,994-363
27 Sept 2026, 23:384,357-631
18 Sept 2026, 20:554,988-753
14 Sept 2026, 07:375,741first reading

Engagement

731 posts held, back to 30 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 65 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.138%
avg views ÷ 24,877 subscribers
Avg views / post
34.3
356 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
356
of 731 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 27 October 2026
Posts held731 (30 July 2026 – 27 October 2026)
Views total12,220
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Oct 2026, 01:29 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

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

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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

“QUICK LINE 247” (@Quickline247), 24,877 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/Quickline247.

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.