Telegram RegisterThe public register of Telegram
Telegram profile photo for Kroc Blanc 🐺

Channel

Kroc Blanc 🐺

@Krocblanc

On this record: Growth Β· Engagement Β· What this channel posts Β· Reactions Β· Posts Β· Citations Β· Cite this entry

6,762subscribers

-60 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001262593542
TypeChannel
Username@Krocblanc
Created7 June 2019 β€” measured β€” cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live4 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/Krocblanc

Growth

6,7626,8226,7926 August 2026 β€” 6,822 subscribers6 August 2026 β€” 6,820 subscribers10 August 2026 β€” 6,818 subscribers12 August 2026 β€” 6,800 subscribers16 August 2026 β€” 6,796 subscribers20 August 2026 β€” 6,791 subscribers23 August 2026 β€” 6,782 subscribers26 August 2026 β€” 6,778 subscribers29 August 2026 β€” 6,777 subscribers1 September 2026 β€” 6,768 subscribers4 September 2026 β€” 6,762 subscribers6 August 20264 September 2026
11 measurements spanning 29 days, net -60. 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 6,753–6,831 and does not start at zero.
Measurement log β€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 18:576,762-6
1 Sept 2026, 10:146,768-9
29 Aug 2026, 07:336,777-1
26 Aug 2026, 09:576,778-4
23 Aug 2026, 10:076,782-9
20 Aug 2026, 02:166,791-5
16 Aug 2026, 18:176,796-4
12 Aug 2026, 22:476,800-18
10 Aug 2026, 06:446,818-2
6 Aug 2026, 20:426,820-2
6 Aug 2026, 10:506,822first reading

Engagement

21 posts held, back to 6 May 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 12 pages of Telegram’s post history, 20 posts per page.

ERR Β· 30 days
12.5%
avg views Γ· 6,762 subscribers
Avg views / post
846
1 post measured
Reaction rate
6.15%
reactions Γ· views Β· ER floor
Posts in window
1
of 21 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 18 August 2026
Posts held21 (6 May 2026 – 18 August 2026)
Views total846
Reactions total52
Forwards / commentsnot exposed by the public surface β€” not measured, not estimated
Readings taken20 Aug 2026, 04:28 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

Video runtime
28s
Average length
28s

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

Reaction mix

905 reactions across 19 posts, in 14 distinct kinds. The most used accounts for 25.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
πŸ‘23425.9%
🀣17018.8%
πŸ”₯16117.8%
❀14115.6%
πŸ‘667.29%
πŸ‘€535.86%
πŸŽ‰293.20%
πŸ’―222.43%
😁111.22%
😈60.663%
🌚50.552%
πŸ€”50.552%
πŸ’”10.11%
🀩10.11%

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 19 of the 21 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 905 reactions in total: the kind of figure the paragraph above means by β€œa reaction total printed elsewhere on the page”.

Measured over the 21 most recent posts we hold, published 6 May 2026 to 18 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

18 Aug 2026, 14:51 UTC846 views52 reactionsread 20 August 2026

https://x.com/KbgStream/status/2089726692935729490

❀31πŸ”₯10πŸ’―5πŸ‘4🀣2

27 Jul 2026, 09:44 UTCβ‰ˆ2,660 views27 reactionsread 20 August 2026

https://x.com/KbgStream/status/2081675636809113638

πŸ”₯15πŸ’―9❀3

11 Jul 2026, 15:09 UTCβ‰ˆ4,990 views82 reactionsread 20 August 2026
Photo

πŸ€“πŸ‘€

πŸ‘46πŸ‘€20❀12πŸ‘4

8 Jul 2026, 09:53 UTCβ‰ˆ4,960 views34 reactionsread 20 August 2026

je cherche des gens qui ont pas vu Citizen Vigilante

πŸ‘29πŸ‘€5

8 Jul 2026, 09:06 UTCβ‰ˆ4,680 views32 reactionsread 20 August 2026

j'ai sorti une vidΓ©o tot ce matin, du coup elle bide, merci de la regarder en entier si possible, dans le cas oΓΉ vous l'auriez ratΓ© : https://youtu.be/hVA9WTodEXY

❀18πŸ‘14

23 Jun 2026, 09:31 UTCβ‰ˆ4,820 views76 reactionsread 20 August 2026

j'ai mΓͺme pas pensΓ© Γ  mettre l'album en mp3 sur le site, y en a qui le voudraient ?

πŸ‘52πŸ”₯14❀10

22 Jun 2026, 14:26 UTCβ‰ˆ4,880 views98 reactionsread 20 August 2026
Video

Krocblanc.fr

🀣86😁6❀2🌚2πŸ‘1πŸ’”1

19 Jun 2026, 16:42 UTCβ‰ˆ4,410 views35 reactionsread 20 August 2026

REBRAND : https://krocblanc.fr/preventes/

πŸ‘19πŸ”₯14πŸ‘2

19 Jun 2026, 11:27 UTCβ‰ˆ3,780 views50 reactionsread 20 August 2026
Photo

Photo, posted without a caption

πŸ”₯26πŸ‘€10πŸ‘4πŸ’―4πŸ€”3❀2🀩1

14 Jun 2026, 18:22 UTCβ‰ˆ4,530 views24 reactionsread 20 August 2026

https://www.youtube.com/live/d_o0A2UlD2k?is=OcLIx099P0ka-WFM

πŸ”₯23❀1

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

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.

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 4 September 2026 β€” this entry's latest reading, not the date you are reading this.

β€œKroc Blanc πŸΊβ€ (@Krocblanc), 6,762 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/Krocblanc.

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.