Telegram RegisterThe public register of Telegram

Channel

֪ ♡゙ 𝗜𝗻𝘧𝘰໒

@Infosugarn

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

264subscribers

+1 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003779354615
TypeChannel
Username@Infosugarn
Created18 April 2026measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/Infosugarn

Growth

263264263.58 Aug 2026, 15:45 — 263 subscribers8 Aug 2026, 21:30 — 264 subscribers8 Aug 2026, 15:458 Aug 2026, 21:30
2 measurements taken within a single day, net +1. 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 263–264 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 21:30264+1
8 Aug 2026, 15:45263first reading

Engagement

11 posts held, back to 18 April 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
67.8%
avg views ÷ 264 subscribers
Avg views / post
179
1 post measured
Reaction rate
0.559%
reactions ÷ views · ER floor
Posts in window
1
of 11 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 5 August 2026
Posts held11 (18 April 20265 August 2026)
Views total179
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 15:45 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.

Reaction mix

1,957 reactions across 10 posts, in 9 distinct kinds. The most used accounts for 20.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 546552045310577414839720.3%
custom 546542723943055402032916.8%
custom 546565007092380003229815.2%
custom 524480923917985604524212.4%
custom 546301604049560750922511.5%
custom 546523620787516033820510.5%
custom 53459944510157262571025.21%
custom 5193193460382858490985.01%
custom 5314720333117284046613.12%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 10 of the 11 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 1,957reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 18 April 2026 to 5 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

5 Aug 2026, 12:37 UTC179 views1 reactionsread 8 August 2026
Sticker

Sticker, posted without a caption

custom 54652362078751603381

26 Jun 2026, 14:48 UTC721 views182 reactionsread 8 August 2026

Кто хочет в фав лист ?? 🎀 не стесняемся Актуально всегда

custom 546565007092380003252custom 546552045310577414851custom 546523620787516033849custom 546542723943055402030

21 May 2026, 19:15 UTC949 views282 reactionsread 8 August 2026
Forwarded from @youandfavPhoto

( ❕ ) ↹ чико & фуюко — канон ♡゙

custom 546542723943055402065custom 546552045310577414865custom 524480923917985604564custom 546565007092380003249custom 546301604049560750939

17 May 2026, 15:54 UTC837 views347 reactionsread 8 August 2026

Posted without readable text

custom 546542723943055402080custom 546523620787516033862custom 546552045310577414862custom 546301604049560750954custom 546565007092380003245custom 524480923917985604544

17 May 2026, 15:49 UTC784 views2 reactionsread 8 August 2026
Sticker

Sticker, posted without a caption

custom 54630160404956075092

17 May 2026, 15:49 UTC812 views380 reactionsread 8 August 2026

Do you know who I am 🤩🤩 🌟🤩🦷🤩🤩🤩🤩🪦🎀our options 🔹од этим постом вы можете написать свои впечатления о моем инфо & обо мне🥹🥹 Unreasonable negative opinion deleted ❤️ 🤩🤩🤩🤩🤩 чико вас любит 🔔

custom 546552045310577414884custom 546301604049560750966custom 546542723943055402064custom 524480923917985604544custom 534599445101572625742custom 519319346038285849040custom 546565007092380003240

17 May 2026, 15:47 UTC785 views5 reactionsread 8 August 2026
Sticker

Sticker, posted without a caption

custom 54630160404956075095

17 May 2026, 15:47 UTC835 views366 reactionsread 8 August 2026
Photo

I love ...🤩🤩 🪦🤩🤩🪦🪧🤩𝒶𝓌 𝓁𝒾𝓈𝓉 🌟🌟🌟 🗝🎀y 𝒹𝑒𝒶𝓇 𝒻𝓇𝒾𝑒𝓃𝒹𝓈 🤍🤍 𝔉uyuko , 𝔥oku , , Linnw ,, виви🤩🤩🤩 Faw list infocm 🤩🤩 @ Мартсевв ,, @ Рен ,, @ Диша ,, @ Девятка ,, @ Минсу ,, @ Аиша ,, @ Цукаса ,, @ Нася @ Юкара ,, @ Вилка ,, @ Нежняша ,, @ Аришкина ,, @ миочан ,, @ Нанами ,, @ Аньчик ,, @Трускавка ,, @ кабачок ,, @ Вульф ,, @ Силли ,, @ сема ,, @ Куке ,, @ Флори ,, @ Рин ,, @ Харико ,, @ Бона , @ Катоня ,, @ Варежка

custom 546565007092380003278custom 546523620787516033860custom 546552045310577414855custom 531472033311728404630custom 524480923917985604529custom 534599445101572625729custom 546301604049560750929custom 519319346038285849028

17 May 2026, 15:47 UTC773 views9 reactionsread 8 August 2026
Sticker

Sticker, posted without a caption

custom 52448092391798560456custom 54656500709238000323

17 May 2026, 15:45 UTC794 views383 reactionsread 8 August 2026
Photo

\`𑁘 ₊ 𝓌𝓌 . cһ𝗶c𝗈 ⁝ ◟𝗌ׄ͜һ𝗲//һ𝗲𝗿!!🎁 // B - day 15.09 🦷 ݁ 𓏲࣪⠀🍬 ꯭ׄ 𝗌ׄ͜𝗉͜𝟗𝗌ׄ͜𝗉͜𝟔𝗌ׄ͜𝗉͜𝟐 ֥‌ 🏹 ︶ᵗ᷒ᰰ ᅠ . 〜 ૮꒰ ⸝⸝´ ˘ ⸝⸝ ꒱ა. 𔓕

custom 546552045310577414880custom 546542723943055402062custom 524480923917985604555custom 546523620787516033833custom 531472033311728404631custom 534599445101572625731custom 546565007092380003231custom 519319346038285849030

Showing the 11 most recent of 11 posts we hold for @Infosugarn. 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 — 1,303,902 of 1,350,102entries 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

Republishes

Channels on the register whose posts this channel has forwarded.

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

“֪ ♡゙ 𝗜𝗻𝘧𝘰໒” (@Infosugarn), 264 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Infosugarn.

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.