Telegram RegisterThe public register of Telegram
Telegram profile photo for 301 Community

Channel

301 Community

@app301

Not marked by Telegram, checked 19 August 2026

On this record: Topic · Channels linked by matching posts · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Domains linked from posts · Cite this entry

2,385,140subscribers

-497,378 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among the largest entries.

Register entry

Telegram ID-1002183253669
TypeChannel
Username@app301
DescriptionPlay now: t.me/Agent301Bot/app Join group: t.me/players301 X (Twitter): x.com/301Community We don’t have NFT collections.
Created29 July 2024 — measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/app301

Topic

Gambling & betting — 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 67% 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.

Growth

2,385,1402,882,5182,633,8296 August 202610 November 2026
64 measurements spanning 96 days, net -497,378. 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 2,310,533–2,957,125 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
10 Nov 2026, 12:192,385,140-6,118
9 Nov 2026, 00:462,391,258-5,510
7 Nov 2026, 20:462,396,768-5,583
6 Nov 2026, 21:262,402,351-4,693
5 Nov 2026, 22:302,407,044-4,815
4 Nov 2026, 22:112,411,859-5,800
4 Nov 2026, 00:552,417,659-4,692
2 Nov 2026, 22:462,422,351-5,916
1 Nov 2026, 19:192,428,267-6,151
31 Oct 2026, 17:202,434,418-6,315
30 Oct 2026, 14:052,440,733-5,862
29 Oct 2026, 17:072,446,595-5,138
28 Oct 2026, 20:192,451,733-5,415
27 Oct 2026, 20:392,457,148-6,641
26 Oct 2026, 16:402,463,789-4,053
25 Oct 2026, 18:062,467,842-2,708
24 Oct 2026, 19:472,470,550-5,233
23 Oct 2026, 20:072,475,783-5,463
22 Oct 2026, 19:102,481,246-7,056
21 Oct 2026, 13:412,488,302first reading

Engagement

417 posts held, back to 29 July 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 4,205 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.342%
avg views ÷ 2,385,140 subscribers
Avg views / post
8,160
61 posts measured
Reaction rate
0.29%
reactions ÷ views · ER floor
Posts in window
61
of 417 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 59 of 61 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 November 2026
Posts held417 (29 July 2024 – 10 November 2026)
Views total497,666
Reactions total1,395
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 05:46 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
116
Videos
2
Links
26

Lifetime counters from Telegram’s own channel header, read 11 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.

View velocity

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 61 of this channel’s own posts over the last 30 days: across 56 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 22 hours of being posted; a typical post has already reached 19.1% of its 24-hour view count within the first hour, and 50.2% within the first six; the median 24-hour reach across those posts is 4,075 views — 0.171% of this channel’s own subscriber count (90th percentile 4,425).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/70710 Nov 2026, 17:53 UTC1976 seconds – 12 hours old2,020 views ~11 reactions60 minutes: 707 interp. → 3.0 hours: 1,200 → 6.0 hours: 1,496 interp. → 12 hours: 2,020still climbing at last readingnot yet at 24h2.1 hoursprovisional — final view count still climbing
/70610 Nov 2026, 17:09 UTC2012 minutes – 13 hours old2,370 views ~11 reactions60 minutes: 868 interp. → 3.0 hours: 1,479 interp. → 6.0 hours: 1,860 → 12 hours: 2,290still climbing at last readingnot yet at 24h1.7 hoursprovisional — final view count still climbing
/7059 Nov 2026, 13:59 UTC6821 minutes – 40 hours old4,720 views ~33 reactions60 minutes: 828 → 3.0 hours: 1,405 interp. → 6.0 hours: 1,960 → 12 hours: 2,390 → 24 hours: 3,280still climbing at last reading3,280measured11 hours
/7046 Nov 2026, 16:30 UTC18310 minutes – 5 days old9,060 views ~62 reactions60 minutes: 785 interp. → 3.0 hours: 1,389 interp. → 6.0 hours: 1,820 → 12 hours: 2,220 → 24 hours: 3,230 → 2 days: 4,630still climbing at last reading3,230measured46 hours
/7035 Nov 2026, 18:28 UTC21321 minutes – 5 days old10,400 views ~49 reactions60 minutes: 915 interp. → 3.0 hours: 1,510 → 6.0 hours: 1,860 → 12 hours: 2,460 → 24 hours: 3,930 → 2 days: 5,570still climbing at last reading3,930measured41 hours
/7025 Nov 2026, 17:33 UTC2236 minutes – 6 days old9,390 views ~16 reactions60 minutes: 974 interp. → 3.0 hours: 1,780 → 6.0 hours: 2,260 → 12 hours: 2,740 → 24 hours: 4,080 → 2 days: 5,400still climbing at last reading4,080measured35 hours
/7013 Nov 2026, 15:37 UTC2583 minutes – 7 days old10,400 views ~45 reactions60 minutes: 708 interp. → 3.0 hours: 1,266 interp. → 6.0 hours: 1,710 → 12 hours: 2,110 → 24 hours: 3,180 → 2 days: 4,410 → 7 days: 10,400views have flattened out3,180measured2 days
/7002 Nov 2026, 13:23 UTC27427 minutes – 7 days old9,880 views ~37 reactions60 minutes: 632 → 3.0 hours: 1,140 → 6.0 hours: 1,850 → 12 hours: 2,340 → 24 hours: 3,160 → 2 days: 5,070 → 7 days: 9,870still climbing at last reading3,160measured46 hours

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.

Reaction mix

11,245 reactions across 306 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤11,245100.0%

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 413 of the 417 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 1,621,369 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 417 most recent posts we hold, published 29 July 2024 to 10 November 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.

Telegram Stars

Stars received
154
across the posts below
Posts paid on
75
of 415 we hold a reading for · 18%
Most on one post
9
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @app301. 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 417 most recent posts we hold for this entry, published 29 July 2024 to 10 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 61 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).

10 Nov 2026, 17:53 UTC≈2,020 views11 reactionsread 11 November 2026
Photo

🍀 Luck voucher ×3 For a whole hour, epic and legendary cars in Brichka drop 3× as often. Only 500 vouchers — grab yours before they’re gone. Drop a like❤️ so we post the next voucher as soon as possible!

❤11

10 Nov 2026, 17:09 UTC≈2,370 views11 reactionsread 11 November 2026
Photo

Быстрый конкурс на маску Итоги через 2 часа

❤11

9 Nov 2026, 13:59 UTC≈4,720 views33 reactionsread 11 November 2026
Photo

⚡ Freebet for ? GRAM Number of activations: 1,000 Tap the button below this post to get Gram credited to your balance

❤33

6 Nov 2026, 16:30 UTC≈9,060 views62 reactionsread 11 November 2026
Photo

🚀 A free 10 Stars Crash bet Number of activations: 1,000 Tap the button below this post — the bet is on us, whatever you win is yours

❤62

5 Nov 2026, 18:28 UTC≈10,400 views49 reactionsread 11 November 2026
Photo

💎 Voucher for 0.1 GRAM Grab 0.1 GRAM to your GRAM balance in Brichka — buy cars and plates on the market, race drag for GRAM or withdraw to your wallet. Only 500 vouchers — be quick before they’re gone. Drop a like❤️ so we post the next voucher as soon as possible!

❤49

5 Nov 2026, 17:33 UTC≈9,390 views16 reactionsread 11 November 2026
Photo

⚡ Freebet for ? GRAM Number of activations: 1,000 Tap the button below this post to get Gram credited to your balance

❤16

3 Nov 2026, 15:37 UTC≈10,800 views45 reactionsread 11 November 2026
Photo

💸 Voucher for ₽5,000 Grab ₽5,000 to your Brichka balance — spin plates, tune and wash your cars. Only 1,000 vouchers — be quick before they’re gone. Drop a like❤️ so we post the next voucher as soon as possible!

❤45

2 Nov 2026, 13:23 UTC≈10,700 views37 reactionsread 11 November 2026
Photo

🍀 Luck voucher ×4 For a whole hour, epic and legendary cars in Brichka drop 4× as often. Only 1,000 vouchers — grab yours before they’re gone. Drop a like❤️ so we post the next voucher as soon as possible!

❤37

1 Nov 2026, 21:12 UTC≈10,400 views22 reactionsread 11 November 2026
Photo

🐍 A free 1,000 point Snake run Number of activations: 1,000 Tap the button below this post — the run is on us, whatever you win is yours

❤22

31 Oct 2026, 19:55 UTC≈11,500 views35 reactionsread 11 November 2026
Photo

⚡ Freebet for ? GRAM Number of activations: 1,000 Tap the button below this post to get Gram credited to your balance

❤35

31 Oct 2026, 17:29 UTC≈9,870 views8 reactions1 Starread 11 November 2026
Photo

🍀 Luck voucher ×4 For a whole hour, epic and legendary cars in Brichka drop 4× as often. Only 600 vouchers — grab yours before they’re gone. Drop a like❤️ so we post the next voucher as soon as possible!

❤8

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

Posts recorded as deleted after publishing

We recorded 12 posts on @app301 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
7 August 2026
Most recent seen missing
30 September 2026
Median time before seen missing
3 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 6 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.

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.

Domains linked from posts

2 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.

x.com1 post · 30 July 2026 – 30 July 2026 · example post
youtube.com1 post · 30 July 2026 – 30 July 2026 · example post

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

“301 Community” (@app301), 2,385,140 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/app301.

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.