Telegram RegisterThe public register of Telegram
Telegram profile photo for ARSENAL

Channel

ARSENAL

@london_arsenal_uz

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Cite this entry

59,555subscribers

+2,107 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1001362592706
TypeChannel
Username@london_arsenal_uz
DescriptionBiz - Arsenal muxlislarimiz. Yangi mavsumni birga o'tkazamiz ❤️ Fan channel, is not an official representative. Reklama: https://t.me/adsnice @menejer_kanalov @Social_Energy_UZ Jadval va narx: tg.segroup.me?uz
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live16 November 2026
Measurements held59
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/london_arsenal_uz

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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

54,31198,18476,247.513 August 2026 — 57,448 subscribers14 August 2026 — 57,152 subscribers15 August 2026 — 56,721 subscribers16 August 2026 — 55,903 subscribers17 August 2026 — 55,606 subscribers18 August 2026 — 55,172 subscribers19 August 2026 — 54,909 subscribers20 August 2026 — 54,609 subscribers22 August 2026 — 54,311 subscribers23 August 2026 — 64,148 subscribers25 August 2026 — 65,769 subscribers26 August 2026 — 65,453 subscribers27 August 2026 — 70,941 subscribers28 August 2026 — 70,926 subscribers29 August 2026 — 71,707 subscribers30 August 2026 — 72,316 subscribers31 August 2026 — 74,135 subscribers1 September 2026 — 75,003 subscribers2 September 2026 — 76,832 subscribers3 September 2026 — 77,519 subscribers6 September 2026 — 77,225 subscribers9 September 2026 — 81,640 subscribers11 September 2026 — 81,310 subscribers13 September 2026 — 85,475 subscribers15 September 2026 — 85,097 subscribers17 September 2026 — 84,838 subscribers19 September 2026 — 84,548 subscribers26 September 2026 — 94,052 subscribers4 October 2026 — 97,714 subscribers9 October 2026 — 98,184 subscribers13 October 2026 — 93,592 subscribers14 October 2026 — 97,230 subscribers15 October 2026 — 96,399 subscribers16 October 2026 — 95,255 subscribers17 October 2026 — 93,672 subscribers18 October 2026 — 92,998 subscribers19 October 2026 — 91,860 subscribers21 October 2026 — 90,032 subscribers22 October 2026 — 88,063 subscribers23 October 2026 — 86,987 subscribers24 October 2026 — 85,353 subscribers25 October 2026 — 84,456 subscribers26 October 2026 — 83,040 subscribers27 October 2026 — 81,778 subscribers28 October 2026 — 80,748 subscribers29 October 2026 — 79,011 subscribers30 October 2026 — 77,347 subscribers31 October 2026 — 76,439 subscribers1 November 2026 — 75,275 subscribers2 November 2026 — 74,762 subscribers3 November 2026 — 73,756 subscribers4 November 2026 — 72,817 subscribers5 November 2026 — 72,231 subscribers6 November 2026 — 71,596 subscribers7 November 2026 — 70,258 subscribers8 November 2026 — 68,418 subscribers10 November 2026 — 66,387 subscribers12 November 2026 — 63,760 subscribers16 November 2026 — 59,555 subscribers59,55513 August 202616 November 2026
59 measurements spanning 95 days, net +2,107. 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 47,730–104,765 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 59
Measured (UTC)SubscribersChange
16 Nov 2026, 07:0159,555-4,205
12 Nov 2026, 15:4763,760-2,627
10 Nov 2026, 10:4666,387-2,031
8 Nov 2026, 22:3568,418-1,840
7 Nov 2026, 14:0170,258-1,338
6 Nov 2026, 12:1571,596-635
5 Nov 2026, 10:1972,231-586
4 Nov 2026, 10:1672,817-939
3 Nov 2026, 12:5673,756-1,006
2 Nov 2026, 13:5674,762-513
1 Nov 2026, 10:2975,275-1,164
31 Oct 2026, 14:0076,439-908
30 Oct 2026, 14:2977,347-1,664
29 Oct 2026, 12:2979,011-1,737
28 Oct 2026, 09:3080,748-1,030
27 Oct 2026, 08:5581,778-1,262
26 Oct 2026, 08:2883,040-1,416
25 Oct 2026, 05:3584,456-897
24 Oct 2026, 07:0585,353-1,634
23 Oct 2026, 04:2686,987first reading

Engagement

210 posts held, back to 1 August 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 194 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
37.1%
avg views ÷ 59,555 subscribers
Avg views / post
22,100
39 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
39
of 210 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 15 November 2026
Posts held210 (1 August 2026 – 15 November 2026)
Views total862,260
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 07:20 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.

What this channel posts

Photos
≈3,100
Videos
≈130
Links
≈2,800

Lifetime counters from Telegram’s own channel header, read 18 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
2m 41s
Average length
23s

Measured directly from 7 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.

Recent posts

Telegram’s own ‘edited’ marker: 4 of 39 posts held from the last 30 days (10.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

15 Nov 2026, 17:50 UTC≈26,000 viewsread 18 November 2026
Photo

🗣 Mish-mishlarga ko‘ra, Bukayo Saka va Tolami Benson unashtiruvni buzishgan, chunki u Hakimiyning stsenariysi bo‘yicha yurmoqchi bo‘lgan, ammo ayoli bunga rozi bo‘lmagan. ❌ Mish-mishlarga ko'ra, Saka nikohni ma'lum shartlar, jumladan nikoh shartnomasi asosida xohlagan, ammo Tolami bu shartlarni qabul qilishga tayyor emasligi aytilgan. 🏴󠁧󠁢󠁥󠁮󠁧󠁿 ARSENAL

15 Nov 2026, 17:50 UTC≈26,100 viewsread 18 November 2026
Video

💇 Rayyaning yangi soch turmagi. 🏴󠁧󠁢󠁥󠁮󠁧󠁿 ARSENAL

15 Nov 2026, 17:50 UTC≈26,100 viewsread 18 November 2026
Photo

⚽️🇸🇪 Viktor Dekeresh "Arsenal" va Shvetsiya terma jamoasi safida joriy mavsumda. Qaniydi u klubda ham shunday gol ura olsa. 🏴󠁧󠁢󠁥󠁮󠁧󠁿 ARSENAL

15 Nov 2026, 15:01 UTC≈27,600 viewsread 18 November 2026
Video

😁😆BONUS SSILKA😁😆 😁😆BONUS SSILKA😁😆 😁😆BONUS SSILKA😁😆

10 Nov 2026, 12:37 UTC≈24,200 viewsread 18 November 2026
Photo

👏 Alan Shirer versiyasi bo'yicha Premer-liga 10-turining ramziy jamoasi. Martin o'z joyida. 🏴󠁧󠁢󠁥󠁮󠁧󠁿 ARSENAL

10 Nov 2026, 12:37 UTC≈24,100 viewsread 18 November 2026
Photo

🇧🇷 Noni Madueke so'nggi o'yinlarda, agar vaziyatlarni amalga oshira olganida edi. 🏴󠁧󠁢󠁥󠁮󠁧󠁿 ARSENAL

9 Nov 2026, 15:41 UTC≈26,500 viewsread 18 November 2026
Photo

✔️ Xalqaro tanaffusga birinchi o'rinda ketmoqdamiz. 🏴󠁧󠁢󠁥󠁮󠁧󠁿 ARSENAL

9 Nov 2026, 15:41 UTC≈26,500 viewsread 18 November 2026
Photo

👏✔️ Deklan Rays oktyabr yakunlari bo'yicha "Arsenal"da oyning eng yaxshi o'yinchisi deb topildi. 🏴󠁧󠁢󠁥󠁮󠁧󠁿 ARSENAL

9 Nov 2026, 15:41 UTC≈26,500 viewsread 18 November 2026
Video

🔥 Dele Alli bahsda yutqazganidan so'ng "Arsenal" futbolkasini yoqib yubordi. 🏴󠁧󠁢󠁥󠁮󠁧󠁿 ARSENAL

9 Nov 2026, 15:41 UTC≈26,600 viewsread 18 November 2026
Photo

🇫🇷 Vilyam Saliba bugun "Arsenal" U-21 jamoasi safida o'ynadi. 🏴󠁧󠁢󠁥󠁮󠁧󠁿 ARSENAL

6 Nov 2026, 16:21 UTC≈24,900 viewsread 18 November 2026
Photo

🇪🇸🏴󠁧󠁢󠁥󠁮󠁧󠁿 «Барселона» определила защитника «Арсенала» Инкапье как потенциальное УСИЛЕНИЕ в январское ТО — SPORT

6 Nov 2026, 16:21 UTC≈25,000 viewsread 18 November 2026
Photo

⚠️ Микель Артета заявил, что Букайо Сака пропустит несколько недель из-за травмы и не факт, что будет готов к матчу с «МС»

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

Posts recorded as deleted after publishing

We recorded 1 post on @london_arsenal_uz as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
12 September 2026
Most recent seen missing
12 September 2026
Median time before seen missing
5 days
Seen missing in the last 30 days
0

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.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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

“ARSENAL” (@london_arsenal_uz), 59,555 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/london_arsenal_uz.

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.