VAM DROПNУТЬ МУZЫКУ ИLИ NET KOMMENTOV DAЙТЕ NORMALЬNO NE DROПNУ nИХУЯ ЕSLИ NE DADИТЕ NORMALЬNO DAйТЕ NORMALЬNO

Channel
JDFLAG
@jdflag
On this record: Topic · Growth · Engagement · What this channel posts · Stars · Posts · Citations · Cite this entry
20,610subscribers
+483 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 | -1001150307579 |
|---|---|
| Type | Channel |
| Username | @jdflag |
| Description | ИИNN МГМТ: @uunn444 |
| Created | Between 1 May 2018 and 31 January 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/jdflag |
Topic
Music — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 52% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 18:08 | 20,610 | +13 |
| 11 Nov 2026, 18:59 | 20,597 | +15 |
| 9 Nov 2026, 23:07 | 20,582 | +8 |
| 8 Nov 2026, 15:06 | 20,574 | +3 |
| 7 Nov 2026, 06:19 | 20,571 | +9 |
| 6 Nov 2026, 04:30 | 20,562 | +12 |
| 5 Nov 2026, 01:47 | 20,550 | +8 |
| 4 Nov 2026, 04:15 | 20,542 | +3 |
| 3 Nov 2026, 01:11 | 20,539 | +9 |
| 2 Nov 2026, 02:29 | 20,530 | +2 |
| 1 Nov 2026, 03:05 | 20,528 | +15 |
| 31 Oct 2026, 03:19 | 20,513 | -12 |
| 30 Oct 2026, 05:10 | 20,525 | +10 |
| 29 Oct 2026, 08:21 | 20,515 | -6 |
| 28 Oct 2026, 06:30 | 20,521 | -2 |
| 27 Oct 2026, 03:40 | 20,523 | +9 |
| 26 Oct 2026, 02:44 | 20,514 | +5 |
| 25 Oct 2026, 02:36 | 20,509 | +4 |
| 24 Oct 2026, 02:15 | 20,505 | -1 |
| 23 Oct 2026, 00:05 | 20,506 | first reading |
Engagement
41 posts held, back to 25 June 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 86 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 47.7%
- avg views ÷ 20,610 subscribers
- Avg views / post
- 9,830
- 5 posts measured
- Reaction rate
- 0%
- reactions ÷ views · ER floor
- Posts in window
- 5
- of 41 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. It is computed over the 4 of 5 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 14 November 2026 |
|---|---|
| Posts held | 41 (25 June 2026 – 14 November 2026) |
| Views total | 49,150 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 04:15 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
- 393
- Videos
- 132
- Links
- 162
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 2m 21s
- Average length
- 35s
Measured directly from 4 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.
Telegram Stars
- Stars received
- 1,920
- across the posts below
- Posts paid on
- 31
- of 38 we hold a reading for · 82%
- Most on one post
- 711
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @jdflag. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 41 most recent posts we hold for this entry, published 25 June 2026 to 14 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 5 posts held from the last 30 days (0%) 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).
@jdflagnews
уёбище na flextrike sиdиt и kиdaet reportы na moи trэkи. vot neйmёtsя xyesosиkу a saуndklaуd - гоvno eбаnoe, гde za levые reпоrtы moжno snestи trэk za 2 sekуndы
https://on.soundcloud.com/S0ZWg7G5LIzMCDsvvL
https://www.youtube.com/watch?v=DyxsKSv6GmA
Channel photo updated
https://on.soundcloud.com/jUzCbLp4cE8kG0uQ6u
https://on.soundcloud.com/Lxvgx0tCp0gaC1HCkP kaver @RecursiveVision
https://on.soundcloud.com/pDdHrNGeV0SJbdbTCz kaver @RecursiveVision mix @SGCM5
AVTOTЮN KOROLЬ
ОТКRЫLИ ПRЕDZАКАZЫ NА FУТБОLКУ DИК — CLASSIC FIT — Куlиrnая гlаdь 250 г, 100% хlопоk — Шеlkогrаfия sпеrеdи — Жаkkаrdоvая биrkа vnуtrи Zаkаzаtь fуtбоlkу mожnо tоlьkо по пrеdzаkаzу, drопа nе буdеt. Пrеdzаkаzы оtkrыtы dо 30 чиslа. К kажdоmу zаkаzу поlожиm sеkrеtnый поdаrоk. jdflag.com
ПОVТОR JDFLAG RОБLОКS КОNЦЕRТА V RОБLОКSЕ БУDЕТ ZАVТRА V 20:00 УЖЕ VМЕSТЕ S FLАГОМ!! ЖDЕМ VSЕХ ZАVТRА! LОББИ МЕRЧ @jdflagcommunity
Showing the 12 most recent of 41 posts we hold for @jdflag. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
@jdflagcommunity · 1,0044 postsmynameismxnc
@maiXencebs · 1752 postsSGCM
@SGCM5 · 7931 post1403.METAL
@TRAPAKALKYLATOR · 1781 postdamage(xxo)
@damagexxo · 3661 postDannyMean
@dannymean4lv3 · 541 postfragile archive
@geezexARCHIVE · 21 postgud0k
@gudokgang · 761 postFLAГ NЬЮWS
@jdflagnews · 4,2621 postfamine / rosgate || LAUREN MIRAGE
@rosgate · 1861 postscharlone
@scharlon21 · 71 post@scrysoda#106#дарксайд
@scrysoda106 · 2701 postшадовлувв brat
@shad0wwlife · 561 post@sk1ttyb0y
@sk1ttyboy · 201 postsouthashfield
@south_ashfield · 861 postSXNCORD
@sxncord · 8991 posttw0seven88☠️
@tw0sseven88 · 611 postUpdates Music & News
@updatesmusicxd · 46,9091 postwhobeefme
@whobeefmeMSC · 671 post#Артериямертвый
@xewixxx · 341 post墓地の ハキラ
@zxcxysos · 1331 post
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 13 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.
@scmusicrus · 14,6153 postsSKB
@SKB808 · 8,7933 postssouthashfield
@south_ashfield · 863 postsОР
@opemopem · 4072 postsdamage(xxo)
@damagexxo · 3661 postfaithmauch mix
@faithmauchmix · 211 postиsportish
@hsitropsi · 7901 postМейнстрим Мьюзик
@mainstreamusic · 11,4921 postMT™
@mt_trademark · 71 post@перк #200
@percarchive · 1441 postРиБ
@rhymebeat · 1,4251 postscharlone
@scharlon21 · 71 postVSRAP Community
@Vsrapcom · 110,4761 post
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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“JDFLAG” (@jdflag), 20,610 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/jdflag.
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.