Telegram RegisterThe public register of Telegram

Channel

Telegram Crawler

@tgcrawl

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

4,930subscribers

+12 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001151022965
TypeChannel
Username@tgcrawl
DescriptionAutomatically detect changes made to official Telegram sites, clients, etc. Source code: https://github.com/MarshalX/telegram-crawler Statuses: ✅ — added 📝 — modified ❌ — removed 🔄 — renamed 📋 — copied #: t.me/tgcrawl/2 Author: @ilya_marshal
CreatedBetween 1 November 2019 and 31 December 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/tgcrawl

Growth

4,9134,9304,921.55 August 2026 — 4,918 subscribers6 August 2026 — 4,918 subscribers7 August 2026 — 4,913 subscribers10 August 2026 — 4,930 subscribers5 August 202610 August 2026
4 measurements spanning 4 days, net +12. 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 4,910–4,933 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 04:114,930+17
7 Aug 2026, 00:354,913-5
6 Aug 2026, 03:494,918no change
5 Aug 2026, 22:014,918first reading

Engagement

31 posts held, back to 24 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
5.81%
avg views ÷ 4,930 subscribers
Avg views / post
286
31 posts measured
Reaction rate
0.319%
reactions ÷ views · ER floor
Posts in window
31
of 31 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 1 of 31 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 11 August 2026
Posts held31 (24 July 202611 August 2026)
Views total8,873
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 05:05 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
23
Videos
2
Links
24,100

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

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1100.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 1 of the 31 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 31 most recent posts we hold, published 24 July 2026 to 11 August 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.

Recent posts

11 Aug 2026, 20:26 UTC65 viewsread 12 August 2026

New changes of Telegram 📝 android-beta/res/values/strings.xml GitHub · MarshalX/telegram-crawler@df8aa76 #android #client Crawl AI (beta) –––––––––––––––––– - Updated the Android beta build’s internal crash-reporting mapping configuration.

11 Aug 2026, 15:34 UTC95 viewsread 12 August 2026

New changes of Telegram 📝 translation_keys.json GitHub · MarshalX/telegram-crawler@1b26f5f #web_tr Crawl AI (beta) –––––––––––––––––– - Added support for birthday suggestions and birthday-related profile settings. - Introduced personal channel profile controls to add, select, or remove a channel from your account. - Expanded account and settings sections with clearer categories for general, privacy, language, noti

11 Aug 2026, 14:32 UTC102 viewsread 12 August 2026

New changes of Telegram 📝 android-beta/res/values/strings.xml GitHub · MarshalX/telegram-crawler@bd43050 #android #client Crawl AI (beta) –––––––––––––––––– - Updated Android app build metadata for the beta release.

10 Aug 2026, 21:53 UTC144 viewsread 12 August 2026

New changes of Telegram 📝 android-beta/res/values/strings.xml GitHub · MarshalX/telegram-crawler@d266fda #android #client Crawl AI (beta) –––––––––––––––––– - Updated Android beta app resources with a new crash reporting mapping identifier.

10 Aug 2026, 19:14 UTC149 viewsread 12 August 2026

New changes of Telegram 📝 android-beta/res/values/public.xml 📝 android-beta/res/values/strings.xml GitHub · MarshalX/telegram-crawler@2ce4144 #android #client Crawl AI (beta) –––––––––––––––––– - Added new editing and formatting options for articles and rich content, including table styles, button types, link/profile actions, and related labels. - Added a revert action for welcome messages with an explanation that

9 Aug 2026, 14:19 UTC202 viewsread 12 August 2026

New changes of Telegram 📝 translation_keys.json GitHub · MarshalX/telegram-crawler@2f28a17 #web_tr Crawl AI (beta) –––––––––––––––––– - Added a new translation entry related to joining voice chats in Telegram WebK. - Updated the web translation catalog with a newly unsorted string for the voice chat join action.

7 Aug 2026, 23:09 UTC266 viewsread 12 August 2026

New changes of Telegram 📝 translation_keys.json GitHub · MarshalX/telegram-crawler@2b111bb #web_tr Crawl AI (beta) –––––––––––––––––– - Expanded Telegram’s private chat experience with new options for tags, quick replies, reminders, scheduled messages, and Saved Messages organization. - Added support for paid messaging, message fees, Star-based gifts, gift offers, transfers, upgrades, resale, and related notificat

7 Aug 2026, 22:29 UTC248 viewsread 12 August 2026

New changes of Telegram 📝 translation_keys.json GitHub · MarshalX/telegram-crawler@a7ac8df #web_tr Crawl AI (beta) –––––––––––––––––– - Updated and cleaned up private chat translation data across the web and iOS resources. - Removed a large set of obsolete messaging, calls, gifts, stars, wallpapers, privacy, scheduling, and secret chat strings from the translation catalog. - Refreshed localization support for newe

7 Aug 2026, 15:29 UTC247 viewsread 12 August 2026

New changes of Telegram 📝 android-beta/res/values/public.xml 📝 android-beta/res/values/strings.xml GitHub · MarshalX/telegram-crawler@7bfc7a2 #android #client Crawl AI (beta) –––––––––––––––––– - Added a new welcome message feature for chats, including setup, empty-state guidance, limits, and removal hints. - Added support for notifying users when a message or block is unsupported and needs an app update. - Added

7 Aug 2026, 14:30 UTC242 viewsread 12 August 2026

New changes of Telegram 📝 translation_keys.json GitHub · MarshalX/telegram-crawler@f0b4b57 #web_tr Crawl AI (beta) –––––––––––––––––– - Added Telegram Business chat automation controls, including bot connection, permissions, chat selection, and session management. - Added support for bots managing messages, profile, stories, gifts, stars, usernames, and read/delete actions. - Introduced community management featur

6 Aug 2026, 07:24 UTC264 viewsread 12 August 2026

New changes of Telegram 📝 translation_keys.json GitHub · MarshalX/telegram-crawler@1724016 #web_tr Crawl AI (beta) –––––––––––––––––– - Added AI prompt styling text for message composition. - Improved article pasting behavior by handling truncated pasted content and tables. - Added options and status messages for saving chats/messages as HTML, including export success and failure states. - Added support for embedd

4 Aug 2026, 15:42 UTC315 viewsread 12 August 2026

New changes of Telegram 📝 translation_keys.json GitHub · MarshalX/telegram-crawler@da4f346 #web_tr

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

Citation-graph rank

Citation-graph rank — 289,437 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

Named by 5 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Nicegram
@nicegramapp · 1,673,013
Telegram ranks this channel #23 of 72 here — alongside 71 others — read 10 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Telegram Crawler” (@tgcrawl), 4,930 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/tgcrawl.

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.