Telegram RegisterThe public register of Telegram

Channel

୨ . . 𝑳𝒐𝒗𝒊𝒏 » 𝒈𝒓𝒐𝒖𝒑 ࿐

@Lovin_group

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

392subscribers

+6 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1004296363293
TypeChannel
Username@Lovin_group
CreatedBetween 1 May 2026 and 30 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/Lovin_group

Growth

3863923897 August 2026 — 386 subscribers8 August 2026 — 386 subscribers8 August 2026 — 390 subscribers15 August 2026 — 392 subscribers7 August 202615 August 2026
4 measurements spanning 8 days, net +6. 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 385–393 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 18:35392+2
8 Aug 2026, 09:17390+4
8 Aug 2026, 06:04386no change
7 Aug 2026, 19:39386first reading

Engagement

18 posts held, back to 30 July 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
182.5%
avg views ÷ 392 subscribers
Avg views / post
715
18 posts measured
Reaction rate
6.18%
reactions ÷ views · ER floor
Posts in window
18
of 18 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 11 of 18 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 7 August 2026
Posts held18 (30 July 20267 August 2026)
Views total12,876
Reactions total622
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 06:04 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

622 reactions across 10 posts, in 9 distinct kinds. The most used accounts for 16.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 520411784284420504610016.1%
custom 52917612375441682359915.9%
custom 53482694522427365617311.7%
custom 54363264952429574287011.3%
custom 52875918937466125236510.5%
custom 5435893008488739080609.65%
custom 5201707945284361930569.00%
custom 5431615238241812827548.68%
custom 5348025038538824974457.23%

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

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

7 Aug 2026, 19:19 UTC64 views17 reactionsread 8 August 2026

Больше актива!

custom 52041178428442050466custom 54358930084887390806custom 52917612375441682353custom 53480250385388249742

Signed . . 𝐈 ꫀꪖႵ ℘ꫀσ℘ᥣꫀ ~~ ࿐ #I_like_it

7 Aug 2026, 13:59 UTC128 views38 reactionsread 8 August 2026

Если готовы ставьте рк!

custom 543632649524295742813custom 52041178428442050467custom 54358930084887390805custom 53482694522427365613custom 52017079452843619302custom 52875918937466125232custom 52917612375441682352custom 53480250385388249742

Signed . . 𝐈 ꫀꪖႵ ℘ꫀσ℘ᥣꫀ ~~ ࿐ #I_like_it

7 Aug 2026, 13:54 UTC134 views95 reactionsread 8 August 2026

Tomorrow...

custom 520411784284420504621custom 534802503853882497418custom 529176123754416823514custom 528759189374661252310custom 52017079452843619307custom 54316152382418128277custom 53482694522427365616custom 54358930084887390806

Signed . . 𝐈 ꫀꪖႵ ℘ꫀσ℘ᥣꫀ ~~ ࿐ #I_like_it

7 Aug 2026, 13:54 UTC132 views0 reactionsread 8 August 2026
Sticker

Sticker, posted without a caption

Signed . . 𝐈 ꫀꪖႵ ℘ꫀσ℘ᥣꫀ ~~ ࿐ #I_like_it

7 Aug 2026, 11:30 UTC125 views11 reactionsread 8 August 2026

так, ну, раз вопросы кончились, закрываю

custom 54358930084887390805custom 53482694522427365614custom 54363264952429574282

Signed Aesaya

7 Aug 2026, 10:24 UTC164 views25 reactionsread 8 August 2026
Photo

▫️🌊🌊🤩🎀𝗻ꪮ𝗻 𝘁ỉ𝗺ᥱ🤩🪦🥰 ▫️ 🪦[🐚]🤩𝗹ꪮ𝘃ỉ𝗻 c𝘃g🤩💙 :🎀sᥙpᥲ dᥙpᥲ 𝗹ᥙv, lᥙ𝘃, 𝗹ᥙv 🤩🪦 ▫️🌸🤩Wỉ𝘁h 🪦 🐚 🤩 𝑨𝒆𝒔𝒂𝒚𝒂🤩 ▫️🤩Qᥙᥱs𝘁ỉꪮ𝗻s?🤩w𝗿ỉ𝘁ᥱ hᥱ𝗿ᥱ 🪦🥹🤩 Bꪮ𝘁 @AesayaAnonBot🐚

custom 53480250385388249746custom 53482694522427365615custom 52875918937466125233custom 54316152382418128273custom 52017079452843619302custom 52917612375441682352custom 54358930084887390802custom 52041178428442050461

7 Aug 2026, 07:27 UTC201 viewsread 8 August 2026
Forwarded from @CharMooreGGPhoto

🪽 ᯓ🤩ɦαɾ🤩 ゙⃞ִഠഠ ִཞ౿⋆ ִֶָ ๋ 🪽 🤩ཞഠບ༩ 🤩 🪦🎀🤩🎀🪦🎀🤩🪦🎀🎀💝🎀🪦 🤩αɓƴ, ƴσυ ϲαɳ ϲσɱϱ αɳ∂ ѕϱϱ ɱϱ🤩 🎀🤩🪦🌟ս᥉γ :: 🤩𐌳ተተ𐍅 🎀 🪦🎀 🎀 💀 🌟ʀ૯૯ :: 🤩𐌵𑀉𐌉ꤕ 🤩ꤕ𑀉𑀉ꤕ 🤩𐌳𐌽ꤕ𐌵𑀉 🤩αƙɩɳɠ🤩ϱνϱɼƴɓσ∂ƴ ɠσ, "ѡɧσ ɩѕ ѕɧϱ?" 🔤ⲥя υⲏⲫⲟⲣⲙⲁцυя ⲃ ⲕⲟⲙⲙⲉⲏⲧⲁⲣυяⲭ... 📰 :: @CharMooreGG ⲃⲟⲧ 📺:: —— ⲃⲟⲟⲋⲧ

5 Aug 2026, 09:01 UTC418 views44 reactionsread 8 August 2026

Правила тут

custom 543161523824181282719custom 520170794528436193013custom 543589300848873908012

5 Aug 2026, 09:00 UTC≈1,620 views208 reactionsread 8 August 2026
Photo

▫️🌊🌊🤩 🎀ꪮнкᥡрс 🤩🪦🥰 ▫️ 🪦[🐚]🤩𝗹ꪮ𝘃ỉ𝗻 c𝘃g🤩💙 🥹🎀sᥙpᥲ dᥙpᥲ 𝗹ᥙv, lᥙ𝘃, 𝗹ᥙv 🤩🪦 🌸🤩𝟏 ოᥱстꪮ 🪦 🐚 🤩 300⭐️🤩 ▫️🤩𝟐 ოᥱстꪮ & 200 . .🤩звёзд 🌊 🤩 𝟑 ოᥱстꪮ || 100 ⭐️ #🤩 ** 🪦🥹🤩 прᥲвилᥲ в 🪦кꪮოო 🐚

custom 529176123754416823566custom 534826945224273656141custom 528759189374661252334custom 520411784284420504617custom 520170794528436193013custom 543589300848873908013custom 543161523824181282712custom 543632649524295742812

Showing the 12 most recent of 18 posts we hold for @Lovin_group. 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 — 19,729 of 1,480,688entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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.

“୨ . . 𝑳𝒐𝒗𝒊𝒏 » 𝒈𝒓𝒐𝒖𝒑 ࿐” (@Lovin_group), 392 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/Lovin_group.

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.