🔧 Heads up: Music's getting an upgrade tomorrow 🔧 Music generation will take a quick nap from 3:00 to 4:00 a.m. EST while we roll it out. Back and better right after. Thanks for hanging tight 🤙
👍1,030🔥1,010❤35custom 523789863250562380413

Channel
@jggl_official
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · View velocity · Reactions · Posts · Citations · Domains linked from posts · Cite this entry
1,929,208subscribers
-83,565 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1002719657055 |
|---|---|
| Type | Channel |
| Username | @jggl_official |
| Description | Welcome to JGGL — the social network for the soundtrack of your life |
| Created | 25 July 2025 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/jggl_official |
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 8 August 2026 and assigned it the closest of 31 fixed categories, at 96% 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. They sit inside a group of 5 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @jggl_official/263 · this entry7 Feb 2026, 19:05 UTC | @philgodlewskii4/1447 Feb 2026, 19:09 UTC | 1.00 | 3 minutes |
| @jggl_official/282 · this entry14 Feb 2026, 20:59 UTC | @philgodlewskii4/25114 Feb 2026, 21:11 UTC | 1.00 | 12 minutes |
| @jggl_official/283 · this entry15 Feb 2026, 21:09 UTC | @philgodlewskii4/25816 Feb 2026, 12:53 UTC | 1.00 | 16 hours |
| @jggl_official/335 · this entry13 Mar 2026, 23:40 UTC | @philgodlewskii4/74613 Mar 2026, 23:43 UTC | 1.00 | 2 minutes |
| @jggl_official/345 · this entry30 Mar 2026, 21:18 UTC | @philgodlewskii4/118831 Mar 2026, 11:44 UTC | 1.00 | 14 hours |
| @jggl_official/348 · this entry2 Apr 2026, 00:38 UTC | @philgodlewskii4/12352 Apr 2026, 00:39 UTC | 1.00 | 2 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @philgodlewskii4 | 13 (8/8 hand-verifiable sample passed) | 1.00 | 31 minutes | this entry (11–2) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 2 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 178 comparable posts for this entry, running 25 July 2025 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 5, the earliest publisher we hold is @jggl_official — which is this entry. That is a statement about our reading window, not a claim of authorship.
On 12 of the 14 posts we watched over 30 days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0111 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /43931 Aug 2026, 10:11 UTC | 31 minutes | 6,860 → 9,750at least +2,880 | 177 → 179at most +3 | +31.9 |
| /43931 Aug 2026, 10:11 UTC | 31 minutes | 9,750 → 12,400at least +2,550 | 179 → 181at most +3 | +28.3 |
| /43931 Aug 2026, 10:11 UTC | 35 minutes | 12,400 → 15,300at least +2,800 | 181 → 182at most +2 | +31.0 |
| /43931 Aug 2026, 10:11 UTC | 34 minutes | 15,300 → 18,500at least +3,100 | 182 → 183at most +2 | +34.4 |
| /43931 Aug 2026, 10:11 UTC | 63 minutes | 18,500 → 24,200at least +5,600 | 183 → 185at most +3 | +62.1 |
| /43931 Aug 2026, 10:11 UTC | 86 minutes | 24,200 → 30,900at least +6,600 | 185 → 192at most +8 | +73.2 |
| /43931 Aug 2026, 10:11 UTC | 70 minutes | 52,900 → 64,300at least +11,300 | 688 → 689at most +2 | +125.2 |
| /43931 Aug 2026, 10:11 UTC | 64 minutes | 64,300 → 94,400at least +30,000 | 689 → 689at most +1 | +332.5 |
| /43931 Aug 2026, 10:11 UTC | 46 minutes | 94,400 → 111,000at least +15,600 | 689 → 689at most +1 | +172.9 |
| /43931 Aug 2026, 10:11 UTC | 41 minutes | 111,000 → 175,000at least +63,000 | 689 → 689at most +1 | +698.3 |
| /43828 Aug 2026, 14:17 UTC | 61 minutes | 5,320 → 9,480at least +4,150 | 202 → 205at most +4 | +46.0 |
| /43828 Aug 2026, 14:17 UTC | 59 minutes | 9,480 → 13,700at least +4,120 | 205 → 210at most +6 | +45.7 |
| /43828 Aug 2026, 14:17 UTC | 65 minutes | 13,700 → 17,900at least +4,100 | 210 → 210at most +1 | +45.4 |
| /43828 Aug 2026, 14:17 UTC | 65 minutes | 17,900 → 21,800at least +3,800 | 210 → 216at most +7 | +42.1 |
| /43828 Aug 2026, 14:17 UTC | 66 minutes | 29,000 → 39,000at least +9,900 | 650 → 652at most +3 | +109.7 |
| /43828 Aug 2026, 14:17 UTC | 46 minutes | 39,000 → 51,000at least +11,900 | 652 → 655at most +4 | +131.9 |
| /43828 Aug 2026, 14:17 UTC | 18 minutes | 51,000 → 59,200at least +8,100 | 655 → 656at most +2 | +89.8 |
| /43828 Aug 2026, 14:17 UTC | 65 minutes | 59,200 → 93,600at least +34,300 | 656 → 656at most +1 | +380.2 |
| /43828 Aug 2026, 14:17 UTC | 65 minutes | 93,600 → 175,000at least +80,400 | 656 → 656at most +1 | +891.1 |
| /4459 Sept 2026, 13:48 UTC | 52 minutes | 4,550 → 5,660at least +1,100 | 45 → 46at most +2 | +12.2 |
| /4459 Sept 2026, 13:48 UTC | 62 minutes | 5,660 → 6,590at least +920 | 46 → 47at most +2 | +10.2 |
| /4459 Sept 2026, 13:48 UTC | 55 minutes | 30,600 → 36,000at least +5,300 | 482 → 482at most +1 | +58.7 |
| /4459 Sept 2026, 13:48 UTC | 61 minutes | 36,000 → 42,700at least +6,600 | 482 → 482at most +1 | +73.2 |
| /4459 Sept 2026, 13:48 UTC | 61 minutes | 57,700 → 68,300at least +10,500 | 1,462 → 1,462at most +10 | +116.4 |
| /4459 Sept 2026, 13:48 UTC | 88 minutes | 68,300 → 80,700at least +12,300 | 1,462 → 1,462at most +10 | +136.3 |
| /44610 Sept 2026, 13:32 UTC | 61 minutes | 2,740 → 4,030at least +1,280 | 27 → 29at most +3 | +14.2 |
| /44610 Sept 2026, 13:32 UTC | 55 minutes | 28,600 → 34,100at least +5,400 | 532 → 532at most +1 | +59.9 |
| /44610 Sept 2026, 13:32 UTC | 61 minutes | 34,100 → 40,800at least +6,600 | 532 → 532at most +1 | +73.2 |
| /44610 Sept 2026, 13:32 UTC | 61 minutes | 56,000 → 66,400at least +10,300 | 1,945 → 1,945at most +10 | +114.2 |
| /44610 Sept 2026, 13:32 UTC | 88 minutes | 66,400 → 79,100at least +12,600 | 1,945 → 1,945at most +10 | +139.7 |
| /44610 Sept 2026, 13:32 UTC | 35 minutes | 97,000 → 115,000at least +17,000 | 1,948 → 1,948at most +10 | +188.4 |
| /44811 Sept 2026, 14:35 UTC | 60 minutes | 2,760 → 4,200at least +1,430 | 33 → 35at most +3 | +15.9 |
| /44811 Sept 2026, 14:35 UTC | 55 minutes | 24,600 → 30,100at least +5,400 | 553 → 554at most +2 | +59.9 |
| /44811 Sept 2026, 14:35 UTC | 61 minutes | 30,100 → 37,000at least +6,800 | 554 → 554at most +1 | +75.4 |
| /44811 Sept 2026, 14:35 UTC | 61 minutes | 52,400 → 63,000at least +10,500 | 1,625 → 1,625at most +10 | +116.4 |
| /44811 Sept 2026, 14:35 UTC | 88 minutes | 63,000 → 75,800at least +12,700 | 1,625 → 1,625at most +10 | +140.8 |
| /45115 Sept 2026, 14:47 UTC | 50 minutes | 3,440 → 4,690at least +1,240 | 21 → 21at most +1 | +13.7 |
| /45115 Sept 2026, 14:47 UTC | 65 minutes | 119,000 → 141,000at least +21,000 | 2,047 → 2,047at most +10 | +232.8 |
| /45115 Sept 2026, 14:47 UTC | 65 minutes | 141,000 → 174,000at least +32,000 | 2,047 → 2,047at most +10 | +354.7 |
| /45318 Sept 2026, 12:31 UTC | 12 hours | 14,600 → 17,200at least +2,500 | 185 → 188at most +4 | +27.7 |
| /45318 Sept 2026, 12:31 UTC | 12 hours | 23,700 → 29,300at least +5,500 | 196 → 203at most +8 | +61.0 |
| /45318 Sept 2026, 12:31 UTC | 12 hours | 29,300 → 141,000at least +110,700 | 203 → 283at most +81 | +1227.0 |
| /4414 Sept 2026, 14:04 UTC | 65 minutes | 79,000 → 94,900at least +15,800 | 1,780 → 1,780at most +10 | +175.1 |
| /4414 Sept 2026, 14:04 UTC | 45 minutes | 108,000 → 129,000at least +20,000 | 1,780 → 1,780at most +10 | +221.7 |
| /4426 Sept 2026, 10:17 UTC | 65 minutes | 74,200 → 89,800at least +15,500 | 720 → 720at most +1 | +171.8 |
| /4426 Sept 2026, 10:17 UTC | 45 minutes | 103,000 → 125,000at least +21,000 | 720 → 720at most +1 | +232.8 |
| /4448 Sept 2026, 13:41 UTC | 61 minutes | 64,700 → 75,100at least +10,300 | 1,724 → 1,724at most +10 | +114.2 |
| /4448 Sept 2026, 13:41 UTC | 88 minutes | 75,100 → 87,700at least +12,500 | 1,724 → 1,724at most +10 | +138.5 |
Expected is the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say. It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the keys clone_source · view_reaction_decoupling, last confirmed 23 September 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 4 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 06:39 | 1,929,208 | +11,955 |
| 16 Sept 2026, 03:01 | 1,917,253 | -6,841 |
| 14 Sept 2026, 08:37 | 1,924,094 | +2,518 |
| 12 Sept 2026, 17:57 | 1,921,576 | -11,928 |
| 10 Sept 2026, 15:16 | 1,933,504 | -30,747 |
| 7 Sept 2026, 14:40 | 1,964,251 | -16,745 |
| 4 Sept 2026, 15:16 | 1,980,996 | -20,995 |
| 2 Sept 2026, 22:25 | 2,001,991 | -4,371 |
| 1 Sept 2026, 20:46 | 2,006,362 | -4,219 |
| 31 Aug 2026, 18:49 | 2,010,581 | -9,399 |
| 30 Aug 2026, 17:05 | 2,019,980 | -3,277 |
| 29 Aug 2026, 19:05 | 2,023,257 | -4,234 |
| 28 Aug 2026, 20:35 | 2,027,491 | -4,538 |
| 27 Aug 2026, 22:24 | 2,032,029 | -2,930 |
| 26 Aug 2026, 22:24 | 2,034,959 | -25,862 |
| 25 Aug 2026, 20:33 | 2,060,821 | -5,583 |
| 24 Aug 2026, 22:59 | 2,066,404 | -7,861 |
| 23 Aug 2026, 06:39 | 2,074,265 | +1,646 |
| 21 Aug 2026, 19:05 | 2,072,619 | +14,622 |
| 20 Aug 2026, 14:43 | 2,057,997 | first reading |
231 posts held, back to 25 July 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 3,382 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 21 September 2026 |
|---|---|
| Posts held | 231 (25 July 2025 – 21 September 2026) |
| Views total | 2,491,200 |
| Reactions total | 24,635 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 24 Sept 2026, 06:06 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.
Lifetime counters from Telegram’s own channel header, read 24 September 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.
Measured directly from 38 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.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 14 of this channel’s own posts over the last 30 days: across 14 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 41 hours of being posted; a typical post has already reached 20.0% of its 24-hour view count within the first hour, and 56.7% within the first six; the median 24-hour reach across those posts is 15,100 views — 0.783% of this channel’s own subscriber count (90th percentile 173,940).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /45318 Sept 2026, 12:31 UTC | 3124 minutes – 28 hours old | 14,500 views ~185 reactions | 60 minutes: 2,492 interp. → 3.0 hours: 5,040 → 6.0 hours: 7,380 → 12 hours: 9,970 → 24 hours: 13,000still climbing at last reading | 13,000measured | 5.9 hours |
| /45217 Sept 2026, 18:41 UTC | 4934 minutes – 46 hours old | 19,700 views ~192 reactions | 60 minutes: 2,963 interp. → 3.0 hours: 5,360 → 6.0 hours: 7,220 → 12 hours: 9,260 → 24 hours: 15,200 → 2 days: 19,700still climbing at last reading | 15,200measured | 13 hours |
| /45115 Sept 2026, 14:47 UTC | 5833 minutes – 4 days old | 186,000 views ~2,067 reactions | 60 minutes: 2,887 interp. → 3.0 hours: 5,680 → 6.0 hours: 16,300 → 12 hours: 35,700 → 24 hours: 89,800 → 2 days: 177,000still climbing at last reading | 89,800measured | 26 hours |
| /44914 Sept 2026, 18:55 UTC | 7645 minutes – 5 days old | 177,000 views ~1,582 reactions | 60 minutes: 3,177 interp. → 3.0 hours: 5,620 → 6.0 hours: 7,290 → 12 hours: 9,810 → 24 hours: 18,900 → 2 days: 105,000still climbing at last reading | 18,900measured | 34 hours |
| /44811 Sept 2026, 14:35 UTC | 134under a minute – 7 days old | 108,000 views ~1,645 reactions | 60 minutes: 2,760 → 3.0 hours: 5,260 → 6.0 hours: 7,360 → 12 hours: 9,650 → 24 hours: 13,000 → 2 days: 45,000 → 7 days: 108,000still climbing at last reading | 13,000measured | 2 days |
| /44610 Sept 2026, 13:32 UTC | 15425 minutes – 7 days old | 149,000 views ~1,948 reactions | 60 minutes: 2,628 interp. → 3.0 hours: 5,080 → 6.0 hours: 7,340 → 12 hours: 9,780 → 24 hours: 12,900 → 2 days: 18,500 → 7 days: 149,000still climbing at last reading | 12,900measured | 3 days |
| /4459 Sept 2026, 13:48 UTC | 14817 minutes – 7 days old | 93,700 views ~1,465 reactions | 60 minutes: 3,036 interp. → 3.0 hours: 5,660 → 6.0 hours: 7,935 interp. → 12 hours: 10,200 → 24 hours: 13,600 → 2 days: 18,200 → 7 days: 93,700still climbing at last reading | 13,600measured | 4 days |
| /4448 Sept 2026, 13:41 UTC | 15424 minutes – 7 days old | 97,900 views ~1,726 reactions | 60 minutes: 2,949 interp. → 3.0 hours: 5,524 interp. → 6.0 hours: 8,110 → 12 hours: 10,700 → 24 hours: 15,000 → 2 days: 21,000 → 7 days: 97,900still climbing at last reading | 15,000measured | 5 days |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
77,060 reactions across 47 posts, in 8 distinct kinds. The most used accounts for 21.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤🔥 | 16,538 | 21.5% | |
| 👍 | 15,085 | 19.6% | |
| 🔥 | 14,562 | 18.9% | |
| ❤ | 13,904 | 18.0% | |
| 🤯 | 8,735 | 11.3% | |
| 😍 | 6,431 | 8.35% | |
| 😱 | 977 | 1.27% | |
| custom 5237898632505623804 | 828 | 1.07% |
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.
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 229 of the 231 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 272,424 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 231 most recent posts we hold, published 25 July 2025 to 21 September 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.
🔧 Heads up: Music's getting an upgrade tomorrow 🔧 Music generation will take a quick nap from 3:00 to 4:00 a.m. EST while we roll it out. Back and better right after. Thanks for hanging tight 🤙
👍1,030🔥1,010❤35custom 523789863250562380413
🤙 JGGL — True Stories | Episode 12 🤙 💬 "Our mission is to create things the world has never seen before." 👤 Meet Max, CPO at XRLAB. His team is building a line of devices for the JGGL ecosystem. This episode walks through what's coming: a JGGL Buddy speaker with 360° screens, cameras, and an AI companion, plus headphones that turn a melody hummed on a walk into a finished track in JGGL Lab. 🚀 Just JGGL It. True S…
🔥232❤29custom 523789863250562380412❤🔥8😱7
Posted without readable text
👍211❤38custom 523789863250562380418❤🔥7😍7
🔍 Andy spent the day asking everyone in the office what they're hiding 🔍 All he got back were dodges, weird looks, and zero answers. 👀 Then he found a folder nobody meant for him to see, and inside it, real design sketches. ⚡️ The truth is coming. Very soon.
👍1,040🔥984❤35😍9custom 52378986325056238043
Everyone in the office is whispering about something, and Andy is the only one who doesn't know what. He's about to find out. ⚡️ The investigation begins.
👍806🔥745❤24custom 523789863250562380411
🤙 JGGL video just got an upgrade 🤙 We rebuilt how video generation works. Here's what you can do now. What changed: 🔸 Set a first and last frame, and the model figures out everything that happens in between 🔸 Upload up to four reference photos, and the video builds itself around you or the style you showed it 🔸 Drop in a video reference, and the model picks up its camera movement and its mood 🔸 A simple photo final…
❤498🔥453👍422❤🔥265custom 52378986325056238049
💨 Drift weekend 💨 Engines roaring on the track, a DJ working the set, and our stand turning into its own little party, with games, prizes, and dancing that didn't stop. ⚡️ Different kinds of noise, but somehow it all landed on the same vibe. 🤙 This is what JGGL sounds like on the road. ▶️ App Store ▶️ Google Play
❤564👍540🔥486😍360custom 52378986325056238044
🎧 Her sound took over the whole night city, and nobody else got the invite 🎧 🤙 Start creating in JGGL. ▶️ App Store ▶️ Google Play
🔥360👍344❤321😍229❤🔥215
🤙 JGGL — True Stories | Episode 11 🤙 💭 "The people building this don't always see which parts are hard for everyone else. It's a blind spot." 👤 Meet Anna, marketer for IMBA, our music label. IMBA grew out of JGGL and is built by the same team, music industry people and developers working side by side. Anna's job is pulling the answers out of them and translating that into something everyone outside the team can ac…
👍479❤454❤🔥393😍388custom 523789863250562380418
Video message, posted without a caption
👍659❤644🔥625😍475custom 523789863250562380416
Video message, posted without a caption
❤240👍212🔥184😍57custom 523789863250562380429
⚡️ Look closer ⚡️ JGGL is becoming more than an app. 🔥 Stay tuned.
🔥888❤862custom 523789863250562380422🤯6😱5
Showing the 12 most recent of 231 posts we hold for @jggl_official. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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.
31 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“JGGL Official” (@jggl_official), 1,929,208 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/jggl_official.
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.