Telegram RegisterThe public register of Telegram
Telegram profile photo for #fg

Channel

#fg

@elliotsweetheart

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

16subscribers

+0 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1002613677307
TypeChannel
Username@elliotsweetheart
Descriptionwe always deliver
Created15 March 2025measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/elliotsweetheart

Growth

1611 Aug 2026, 14:49 — 16 subscribers11 Aug 2026, 22:31 — 16 subscribers11 Aug 2026, 14:4911 Aug 2026, 22:31
2 measurements taken within a single day. 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 15–17 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 22:3116no change
11 Aug 2026, 14:4916first reading

Engagement

11 posts held, back to 15 March 2025the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 11 posts for this entry, the most recent from 15 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
4
Links
1

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

190 reactions across 6 posts, in 14 distinct kinds. The most used accounts for 20.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54090303373993926663920.5%
custom 63120119711766984573518.4%
custom 52874780427535197233216.8%
💘2613.7%
custom 5470075996067603435178.95%
❤‍🔥147.37%
🎉94.74%
42.11%
31.58%
💯31.58%
🔥31.58%
21.05%
🕊21.05%
😇10.526%

Custom emoji. 4 of the rows above are 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 6 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 190reactions 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 15 March 2025 to 15 July 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

13 Jul 2026, 18:48 UTC189 views2 reactionsread 11 August 2026
Forwarded from @averythemayosoulPhoto

⩩ › WIN ﹠ @BESTIRL ⇉ 𝄒𓏏 главным ирл Дейв Миллер & Джек Кеннеди & Ди Кеннеди & Питер Кеннеди становятя . . . ⠀⠀↳ ⁝ @davevirgin @zusimoto @multifandom_showtime @heartpizza набирая 1973 голосов ! ‹ /Ш

💘2

22 Jun 2026, 11:37 UTC390 views20 reactionsread 11 August 2026

дни && рест ( кроме фг ) 🤩 привет я очень заебался и незнаю почему я раньше этого не написал не пишите мне и не отмечайте вообще нигде ‼️ с шансом 100% я проигнорю вас

❤‍🔥11💯3custom 63120119711766984573💘1🕊1😇1

10 May 2026, 15:13 UTC658 views23 reactionsread 11 August 2026

me 🌟 and fg 🌟🌟🌟as ennea 🤩🤩 me 🤩 and fg 🤩🤩🤩 as stickmen 🤩🤩 me 🙂 and fg 😃🥴🙂 as algebraliens 🤩🤩 me 🌟 and fg 🌟🌟🌟 as dokis 🤩🤩 🌟🌟i love fg🌟🌟🌟🌟

🎉9💘63❤‍🔥3custom 54090303373993926662

6 May 2026, 15:58 UTC706 views51 reactionsread 11 August 2026
Photo

❌❌꒰𓏼´ `𓏼 🤩𝐨𝐯𝑒 𝗹𝗶𝐬t 🥹 🤩 @️фита , @️трисмос , @️айрин , @️нова , @️манго , @️степа , @️кица , @мирра , @️сиоми , @️анч , @️полосатик , фэггэнг , группа слпвм , блядушник . . ! . . порядок не имеет значения ! 😊 ❌❌я люблю вас всех <3

custom 540903033739939266617custom 631201197117669845710custom 52874780427535197239custom 54700759960676034355💘3🔥322

6 May 2026, 15:58 UTC665 views46 reactionsread 11 August 2026
Photo

❌🤩 ヾ 🔤𝗼ur 𝐨𝐩in𝗶𝗼𝗻 ab𝗼𝘂𝐭 m𝗲 ❓ ❌❌ ֺּׅ𓏽⑅ флуд удаляю ! 🤩🤩❌❌

💘14custom 631201197117669845712custom 54090303373993926667custom 54700759960676034356custom 528747804275351972352

6 May 2026, 15:57 UTC663 views48 reactionsread 11 August 2026
Photo

❌❌゛𝐞𝐥li𝗼𝘁 ノ 𝘇uӄִׄ𝐚 ⸝⸝ .ᐟ 🍕 ꒰𐔌 𝐚𝐧𝘆 pr𝙣‌‌s ⋮ 𝟮𝟮.O4 🤩🤩🤩🤩 🤩🤩 𝗜𝗦𝐓𝐉 𝘀𝗽𝟗(w1)𝐬𝐩6𝘴𝗽𝟒 𝑭𝑳𝐄𝐕 🤩 ㅤ⃔᳠ㅤ ِ🤩🤩 ꨲ 𝗽𝗵𝗹eg – me𝗹 [𝐑]l/𝗨/an ֺ › 🥹🥹 𝐬𝐡𝐩 𝗺𝗼𝐫𝐞 𝐜𝐫𝗲𝗱𝗶𝘁s 🤩 ۪𓈒 ຼ ͜𓐇˚ִִ𓈒꒱꒱

custom 528747804275351972318custom 540903033739939266613custom 631201197117669845710custom 54700759960676034356🕊1

Showing the 11 most recent of 11 posts we hold for @elliotsweetheart. 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

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

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.

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

“#fg” (@elliotsweetheart), 16 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/elliotsweetheart.

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.