ะะดะผะธะฝะธัััะฐัะธั -๐ซ ะะฐะฝััะพ -โค๏ธ ะัะพะฝั-๐ ๐๐๐๐๐๐๐ ๐๐๐๐๐๐๐ ๐๐ฅ๐๐ง๐ ๐๐ข๐ฅ๐๐๐ซ๐ญ๐ซ ๐๐๐ซ๐จ๐ฅ๐ข๐ง๐ ๐ ๐จ๐ซ๐โค๏ธ ๐๐๐ญ๐ก๐๐ซ๐ข๐ง๐ ๐๐ข๐๐ซ๐๐โค๏ธ ๐๐จ๐ง๐ง๐ข๐ ๐๐๐ง๐ง๐๐ญ๐ญ ๐๐๐ฑ๐ข ๐๐ซ๐๐ง๐ฌ๐จ๐งโค๏ธ ๐๐๐ง๐ง๐ ๐๐จ๐ฆ๐ฆ๐๐ซ๐ฌ ๐๐ง๐ง๐๐๐๐ฅ๐ฅ๐ ๐๐ข๐๐ค๐ข ๐๐จ๐ง๐จ๐ฏ๐๐ง ๐๐๐ซ๐ฒ ๐๐จ๐ฎ๐ข๐ฌ๐ ๐๐๐๐ข๐ ๐๐๐ญ๐ซ๐จ๐ฏ๐ ๐๐จ๐ซ๐ ๐๐ข๐ฅ๐๐๐ ๐๐ซ๐ ๐๐ฅ๐ข๐ฏ๐ข๐ ๐๐๐ซ๐ค๐๐ซ ๐๐ฆ๐๐ซ๐ ๐๐ฒ๐๐ข๐ฅ ๐๐๐ญ๐ข๐ ๐๐จ ๐๐๐ฎ๐ ๐ก๐ฅ๐ข ๐๐ฅ๐๐ซ๐ข๐ ๐๐๐ฅ๐ญ๐ณ๐ฆ๐๐ง ๐๐๐ฆ๐จ๐ง ๐๐๐ฅ๐ฏ๐๐ญ๐จ๐ซ๐โค๏ธ ๐๐๐ซ๐๐ฆ๐ฒ ๐๐ข๐ฅ๐๐๐ซ๐ญ ๐๐จ๐ฌ๐ก๐ฎ๐ ๐๐๐ซ๐ค๐๐ซ ๐๐๐ข ๐๐๐ซ๐ค๐๐ซ ๐๐ฎ๐๐๐ฌ ๐๐๐ซ๐ค๐๐ซ ๐๐๐ญ๐ญ ๐๐จ๐ง๐จ๐ฏ๐๐ง ๐๐ข๐ฅ๐๐ฌ ๐๐ญ๐๐๐๐ง ๐๐๐ฅ๐ฏ๐๐ญ๐จ๐ซ๐ โค๏ธ ๐๐ฒ๐ฅ๐๐ซ ๐๐จ๐๐ค๐ฐ๐จ๐จ๐ ๐๐ง๐ณ๐จ ๐๐ญ. ๐๐จ๐ง๐ก ๐๐๐ฅ๐๐ซ๐ข๐ ๐โฆ

Channel
Info ๐ต๐ธ๐ฟ๐ฟ๐ผ๐ธ
@infoBELLIE
On this record: Growth ยท Engagement ยท Posts ยท Citations ยท Cite this entry
1subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register ยท movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003976541876 |
|---|---|
| Type | Channel |
| Username | @infoBELLIE |
| Created | 8 May 2026 โ measured โ dated from the channelโs first post |
| First recorded | 15 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/infoBELLIE |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 08:31 | 1 | no change |
| 10 Aug 2026, 18:17 | 1 | first reading |
Engagement
2 posts held, back to 8 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 1 page of Telegramโs post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute โ we hold 2 posts for this entry, the most recent from 8 May 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Channel created
Showing the 2 most recent of 2 posts we hold for @infoBELLIE. 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 3 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.
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 15 August 2026 โ this entry's latest reading, not the date you are reading this.
โInfo ๐ต๐ธ๐ฟ๐ฟ๐ผ๐ธโ (@infoBELLIE), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/infoBELLIE.
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.