Telegram RegisterThe public register of Telegram
Telegram profile photo for рест до 05.09||˚ʚsᥕᥱᥱᴛ fᥣ᧐᧐ɗɞ˚iᥒf᧐

Channel

рест до 05.09||˚ʚsᥕᥱᥱᴛ fᥣ᧐᧐ɗɞ˚iᥒf᧐

@sweetinffo

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

38subscribers

+10 since we began measuring on 15 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003900430274
TypeChannel
Username@sweetinffo
CreatedBetween 1 March 2026 and 14 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live29 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/sweetinffo

Previous handles

@sweetinffo was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@moonligtinf
held 15 August 202615 August 2026

Growth

283933.515 August 2026 — 28 subscribers15 August 2026 — 28 subscribers22 August 2026 — 38 subscribers29 August 2026 — 39 subscribers29 August 2026 — 39 subscribers29 August 2026 — 38 subscribers3815 August 202629 August 2026
6 measurements spanning 15 days, net +10. 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 26–41 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 21:4638-1
29 Aug 2026, 19:1539no change
29 Aug 2026, 19:0239+1
22 Aug 2026, 12:3638+10
15 Aug 2026, 08:4528no change
15 Aug 2026, 08:3228first reading

Engagement

39 posts held, back to 14 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
34.3%
avg views ÷ 38 subscribers
Avg views / post
13.0
38 posts measured
Reaction rate
16.7%
reactions ÷ views · ER floor
Posts in window
39
of 39 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 4 of 38 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 29 August 2026
Posts held39 (14 August 202629 August 2026)
Views total495
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 19:15 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
37s
Average length
37s

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

4 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥375.0%
💘125.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 4 of the 39 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 39 most recent posts we hold, published 14 August 2026 to 29 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

29 Aug 2026, 16:06 UTC5 viewsread 29 August 2026
Forwarded from @fashioninforPhoto

𝘾𝙍𝙐𝙎𝙃 𝙇𝙄𝙎𝙏 я люблю все союзы, но этих немного больше. @miwayakifld @red_stars_top @serene_bliss @klamefloodinfo88 @succsex_official @Tomiyakihotsouceflood @warminfor @poffoosfld @Louisflood @strayflood_offical @bestfriendsflood_channel @hikamori_flood @Aspelifa @skywhispersflood @midnightinfofld @sweetinffo мои любимки❤ увидели себя - рп в инфо. в лс не кидаю.

29 Aug 2026, 10:37 UTC59 viewsread 29 August 2026

#ruka:инфо берёт рест до 5 сентября,там дальше уже подумаю что делать. в чистках сз – не участвуем союзы – принимаем рп – репостить не буду,если что-то срочно надо,то пишите мне в лс. #swtinfo #сзрп

29 Aug 2026, 10:27 UTC6 viewsread 29 August 2026
Forwarded from @V3loul_fluuuuudVideo

ㅤㅤ𓏲࣪ᰍ 𝗡ꫀׄ͠𝘄 𝘂𝗻𝗶ꪮ𝗻ㅤʾʾ ㅤ۟ + @moonligtinf Рада союзу !!

28 Aug 2026, 15:10 UTC9 viewsread 29 August 2026
Forwarded from @miidniightfloodVideo

𝔫𝔢𝔴 𝔳𝔦𝔡𝔢𝔬 id: наша 𝕖𝕕𝕚𝕥𝕠𝕣 : sᴏʏᴇᴏɴ . . #сзрп

28 Aug 2026, 14:54 UTC51 viewsread 29 August 2026

#ruka:союзы,то что надо прорепостить кидайте мне в лс– @mildxsxs потому что у меня много чатов,я не успеваю за ними следить.спасибо за внимание!💓 #swtinfo #сзрп

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

Forward network

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

Names

Channels on the register whose handles appear in this channel's posts.

анджелз
@angellisel · 1
1 post
*̣̥·͙̥♡‧̩୨୧˙˟͙𝐀𝐬𝐩𝐞𝐥𝐢𝐟𝐚️˟͙˙୨୧‧̩̥♡·͙̥̣*̣̥
@Aspelifa · 187
1 post
рест на рп | Aᥙrᥱᥣiᥲ fᥣ᧐᧐ɗ iᥒf᧐
@aurlflood · 109
1 post
ᯓ ⊹ 𝘉𝘦𝘴𝘵 𝘍𝘳𝘪𝘦𝘯𝘥𝘴 𝘤𝘩𝘢𝘯𝘯𝘦𝘭 ( 24 ) ५ ⊹ ‧
@bestfriendsflood_channel · 205
1 post
𝑯𝑰𝑲𝑨𝑴𝑶𝑹𝑰 𝑭𝑳𝑫
@hikamori_flood · 90
1 post
kᥣᥲⲙᥱ 𐔥ᥣ𐔖𐔖ᦔ ιᥒ𐔥𐔖
@klamefloodinfo88 · 404
1 post
忍者 — 𝗟𝗼𝘂𝗶𝘀 𝗳𝗹𝗼𝗼𝗱 🍕 +𝟬𝟳𝟬
@Louisflood · 91
1 post
Ɫυƞѧɍ ƍѧⱬє ӻƖѳѳđᶦᶰᶠᵒᵒ
@lunarrgaze · 41
1 post
рест♯𝗠îg𐓣įGht * 𝗙l𑄜ꪮg 𝄢 | ` 최고
@midnightinfofld · 165
1 post
𝗠ı᤻ᾤᥲყ𝖺𝗸i᪶᪴ 𝔽ℓoøᤨძ 💚
@miwayakifld · 254
1 post
ⓘ poffoos flood . .
@poffoosfld · 242
1 post
ИНФО — ྀིྀི୨୧ 𐙚 ೀ ℙ𝕦𝕣𝕡𝕦𝕣𝕟𝕪𝕖 𝕠𝕓𝕝𝕒𝕜𝕒 𐙚 𓍼
@ptddgjkvdd · 97
1 post
𝐫𝐞𝐝_𝐬𝐭𝐚𝐫𝐬 𝐢𝐧𝐟𝐨.
@red_stars_top · 214
1 post
РЕСТ | 𝑺𝑬𝑹𝑬𝑵𝑬 𝑩𝑳𝑰𝑺𝑺. (𝒄𝒐𝒏𝒇𝒆𝒓𝒆𝒏𝒄𝒆)
@serene_bliss · 168
1 post
𝑺𝒌𝒚 𝑾𝒉𝒊𝒔𝒑𝒆𝒓𝒔/𝑰𝒏𝒇𝒐
@skywhispersflood · 190
1 post
𝘀𝘁𝗿𝗮𝘆 𝗳𝗹𝗼𝗼𝗱
@strayflood_offical · 96
1 post
Рест сонхун. 🔐
@succsex_official · 272
1 post
Выходной/𝗧𝗼𝗺𝗶𝘆𝗮𝗸𝗶 𝗵𝗼𝘁 𝘀𝗼𝘂𝗰𝗲 𝗳𝗹𝗼𝗼𝗱🌙
@Tomiyakihotsouceflood · 60
1 post
| 𝐈nׅ݁f𑄜 ͜ ︵ω𐐼ׁׅܻ݊𝕣𝅄ꩇׁׅ
@warminfor · 1,424
1 post

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

“рест до 05.09||˚ʚsᥕᥱᥱᴛ fᥣ᧐᧐ɗɞ˚iᥒf᧐” (@sweetinffo), 38 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/sweetinffo.

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.