ูุงุญุฏ ุงูุณูุงู ุนูููู ูุฑุญู ู ุงููู ูุจุฑูุงุชู ุงูุดุจุงุจ ู ููุงุช ู ุฒุงู ุฎุฏุงู ูู ูููู ุงู ูุง โ ๐
โค73๐6๐5

Channel
@chat_BlLAL_Marco
On this record: Growth ยท Engagement ยท What this channel posts ยท Reactions ยท Posts ยท Posts edited after publishing ยท Citations ยท Cite this entry
11,057subscribers
+179 since we began measuring on 7 August 2026
Risers and fallers across the register ยท movement among entries of 10,000โ31,623.
| Telegram ID | -1002165300427 |
|---|---|
| Type | Channel |
| Username | @chat_BlLAL_Marco |
| Created | Between 1 June 2024 and 30 September 2024โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/chat_BlLAL_Marco |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 16:53 | 11,057 | -3 |
| 28 Aug 2026, 16:36 | 11,060 | -3 |
| 27 Aug 2026, 19:53 | 11,063 | -2 |
| 26 Aug 2026, 16:35 | 11,065 | -1 |
| 25 Aug 2026, 14:33 | 11,066 | -3 |
| 24 Aug 2026, 15:24 | 11,069 | -10 |
| 23 Aug 2026, 00:44 | 11,079 | +1 |
| 21 Aug 2026, 13:02 | 11,078 | -1 |
| 20 Aug 2026, 09:02 | 11,079 | +4 |
| 19 Aug 2026, 08:11 | 11,075 | -10 |
| 18 Aug 2026, 09:18 | 11,085 | +2 |
| 17 Aug 2026, 09:38 | 11,083 | -1 |
| 15 Aug 2026, 20:22 | 11,084 | +7 |
| 14 Aug 2026, 12:55 | 11,077 | +2 |
| 13 Aug 2026, 06:47 | 11,075 | -1 |
| 12 Aug 2026, 10:07 | 11,076 | +30 |
| 11 Aug 2026, 07:41 | 11,046 | +70 |
| 10 Aug 2026, 09:01 | 10,976 | +18 |
| 9 Aug 2026, 07:51 | 10,958 | +55 |
| 8 Aug 2026, 06:33 | 10,903 | first reading |
102 posts held, back to 4 August 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 41 pagesof 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 28 August 2026 |
|---|---|
| Posts held | 102 (4 August 2026 โ 28 August 2026) |
| Views total | 303,260 |
| Reactions total | 6,775 |
| Forwards / comments | not exposed by the public surface โ not measured, not estimated |
| Readings taken | 29 Aug 2026, 11:20 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.
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.
6,775 reactions across 102 posts, in 7 distinct kinds. The most used accounts for 86.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| โค | 5,826 | 86.0% | |
| ๐ | 425 | 6.27% | |
| โคโ๐ฅ | 205 | 3.03% | |
| ๐ฅ | 139 | 2.05% | |
| ๐ | 111 | 1.64% | |
| ๐คฉ | 48 | 0.708% | |
| ๐ฅฐ | 21 | 0.31% |
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 102 of the 102 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 6,775reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 102 most recent posts we hold, published 4 August 2026 to 28 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.
ูุงุญุฏ ุงูุณูุงู ุนูููู ูุฑุญู ู ุงููู ูุจุฑูุงุชู ุงูุดุจุงุจ ู ููุงุช ู ุฒุงู ุฎุฏุงู ูู ูููู ุงู ูุง โ ๐
โค73๐6๐5
ู ุณุงุก ุงูุฎูุฑ ุงูุดุจุงุจ ๐ฅ ุบุจุฑุช ุนูููู ูุงุฏ ุงูุฃูุงู ุจุญูู ู ุฑูุถ ู ููููุงุด ุงูููุช ููู ููุงุฏ ููู ุงูู ููุงุช โค๏ธ ูููู ูุดุงุก ุงููู ุงุจุชุฏุฃ ู ู ุงูููู ุบูุฑุฌุน โ ูููู ู ุง ุชููู ุนูุฏู ุดู ูููุชุฉ ููุงุฏ ููู ๐ฏ๐ ุบูุฑ ูุชูู ุง ู ุชุจุฎููุด ุนูููุง ุจุงูุฏุนู ุฏูุงููู ๐๐ฏ
โค150โคโ๐ฅ5๐4๐1
ูุฑุฏูุด ู ุนุตุจ ๐ ุฅูู ู ุชูุงุนูุชูุด ู ุนุงู ุบูุชููู ุนูููู ๐ฅฒ
โค96๐คฉ11
Video, posted without a caption
โค60๐ฅ11๐คฉ9
๐น ู ุณุงุก ุงูุฎูุฑ โ๏ธ ๐น ุงูู ููุงุช ู ู VPS ๐ฉ๐ช๐ ๐นุณุฑุงุน โก๏ธ ๐นูููุฏุนู ู ุงูุฃูุนุงุจ ๐ฎ ๐นุงููุฑุฌุฉ ุจุฌูุฏุฉ ุนุงููุฉ ๐ป ๐นุงูู ุฏุฉ 5 ุฃูุงู ๐ ๐นู ูุงุญุธุฉ โ ๏ธ ๐นุฅูู ู ูุตูุด ูุงุฏ ุงูู ูุดูุฑ 100 โค๏ธโ๐ฅ ูู ูู ู ู 24 ุณุงุนุฉ โผ๏ธ ๐นุบูููู ุฌู ูุน ุงูู ููุงุช ูู ุง ุบูุนุงูุฏ ูุญุท ูุงูู ุญุชู ุฏูุฒ 5 ุฃูุงู ๐จ โฌ๏ธ ู ุชูุณุงูุด ุงูุชูุงุนู ู ุน ุงูู ููุงุช โ ๐น ููุชู ูู ุชูุฏุฑู ูุงุฏ ุงูู ุฌููุฏุงุช ๐
โค146โคโ๐ฅ6๐5๐ฅฐ2๐1
๐นแดแดแด : ษดแดแด แดแดษดษดแดส ๐ต ๐นสแด๊ฑแดแดแด : ษชษดแดกษช ร6 ๐ ๐น๊ฑแดสแด แดส : ษขแดสแดแดษดส ๐ฉ๐ช ๐นแดสแดแดแดแดแดส : ๊ฑ๊ฑส -ssl โ ๐นแดxแดษชสส แด แดแดแด : 5 แด แดส๊ฑ ๐
โค41๐2
๐นแดแดแด : ษดแดแด แดแดษดษดแดส ๐ ๐นสแด๊ฑแดแดแด : ษชษดแดกษช ร6 ๐ ๐น๊ฑแดสแด แดส : ษขแดสแดแดษดส ๐ฉ๐ช ๐นแดสแดแดแดแดแดส : ๊ฑ๊ฑส แดก๊ฑ โ ๐นแดxแดษชสส แด แดแดแด : 5 แด แดส๊ฑ ๐
โค38๐3
๐นแดแดแด : ษดแดแด แดแดษดษดแดส ๐ ๐นสแด๊ฑแดแดแด : ษชแดแด ร6 ๐ ๐น๊ฑแดสแด แดส : ษขแดสแดแดษดส ๐ฉ๐ช ๐นแดสแดแดแดแดแดส : แดสแดแดแดษด โ ๐นแดxแดษชสส แด แดแดแด : 5 แด แดส๊ฑ ๐
โค38๐3โคโ๐ฅ1
๐นแดแดแด : ษดแดแด แดแดษดษดแดส ๐ ๐นสแด๊ฑแดแดแด : ษชแดแด ร6 ๐ ๐น๊ฑแดสแด แดส : ษขแดสแดแดษดส ๐ฉ๐ช ๐นแดสแดแดแดแดแดส : ๊ฑ๊ฑส โ ๐นแดxแดษชสส แด แดแดแด : 5 แด แดส๊ฑ๐
โค37๐3
Sticker, posted without a caption
โค21
๐นแดแดแด : สแดแดแด แดแด๊ฑแดแดแด ๐ ๐นสแด๊ฑแดแดแด : ษชแดแด ร6 ๐ ๐น๊ฑแดสแด แดส : ษขแดสแดแดษดส ๐ฉ๐ช ๐นแดสแดแดแดแดแดส : ssl +sshโ ๐นแดxแดษชสส แด แดแดแด : 5 แด แดส๊ฑ ๐
โค48
๐นแดแดแด : สแดแดแด แดแด๊ฑแดแดแด ๐ ๐นสแด๊ฑแดแดแด : ษชแดแด ร6 ๐ ๐น๊ฑแดสแด แดส : ษขแดสแดแดษดส ๐ฉ๐ช ๐นแดสแดแดแดแดแดส : ssl โ ๐นแดxแดษชสส แด แดแดแด : 5 แด แดส๊ฑ ๐
โค53๐2
Showing the 12 most recent of 102 posts we hold for @chat_BlLAL_Marco. 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.
@chat_BlLAL_Marco edited 1 post after it first published โ the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too โ this register can tell you the wording changed and when, not why. How this is measured.
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.
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 29 August 2026 โ this entry's latest reading, not the date you are reading this.
โ๐๐๐๐๐ ๐๐๐๐๐โ (@chat_BlLAL_Marco), 11,057 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/chat_BlLAL_Marco.
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.