Telegram RegisterThe public register of Telegram
Telegram profile photo for love me

Channel

love me

@love_5213140

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

484subscribers

+31 since we began measuring on 2 September 2026

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

Register entry

Telegram ID-1003932191771
TypeChannel
Username@love_5213140
Created4 June 2026 — measured — dated from the channel’s first post
First recorded2 September 2026
Last confirmed live11 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/love_5213140

Growth

453484468.52 September 2026 — 453 subscribers2 September 2026 — 453 subscribers11 September 2026 — 484 subscribers2 September 202611 September 2026
3 measurements spanning 9 days, net +31. 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 448–489 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 18:18484+31
2 Sept 2026, 12:45453no change
2 Sept 2026, 12:30453first reading

Engagement

16 posts held, back to 4 June 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.

ERR · 30 days
6.61%
avg views ÷ 484 subscribers
Avg views / post
32.0
1 post measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1
of 16 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 2 September 2026
Posts held16 (4 June 2026 – 2 September 2026)
Views total32
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 12: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

20 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 55.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1155.0%
🎉420.0%
👎315.0%
😍210.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 8 of the 16 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 20 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 4 June 2026 to 2 September 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

2 Sept 2026, 07:59 UTC32 viewsread 2 September 2026

新押的公群 新老客户可以进来了 做单无忧 有保障 可以报备 https://t.me/+Wu1dIP9S0Z9kZWVh

16 Aug 2026, 04:09 UTC536 viewsread 2 September 2026
Photo

人在就秒 大众通吃 速度实力并存 钱到位疑难杂症都能干

15 Aug 2026, 15:55 UTC469 views1 reactionsread 2 September 2026

😀时段早晨10:00-凌晨2:00😀 文全😀😀😀 (人在就秒) 公网补齐😀😀😀(任意排除 可十七位) 公网猎魔😀😀😀 (可带任意排除) 老线路、高质量、超丝滑 联系 @lovesadu 诚招代理,价格给到胃

❤1

15 Aug 2026, 03:42 UTC661 viewsread 2 September 2026

支机2u 有量有价 @lovesadu 剩菜支机 看菜来定价 一切通吃 钱到位 各种疑难杂症都能出 破解支百前最后一道防线 @lovesadu 破解支百12u 通吃港澳台、未认证、脱裤、邮箱、大众名、异常号 @lovesadu 近期福利!报支机送假地!

9 Aug 2026, 04:30 UTC556 viewsread 2 September 2026

假地址又砸盘了 降价1u!降价1u! 降价1u!降价1u! 降价1u!降价1u! ui面板不会显示 输入/jdz或者/gh 即可 @lovedejiadizhibot

8 Aug 2026, 14:30 UTC496 viewsread 2 September 2026

假地明天价格上涨回调😀😀 新增最新的套餐会员制! 黄金、铂金、钻石、王者 为尊贵的会员等级 享受最优优势 机器人 @lovedejiadizhibot 秒单 黄金--铂金--钻石--至尊 等级由低到高 黄金用户免费升级 永久不消失 铂金用户历史充值18u 升级铂金特惠并且加20分 永久不消失 熟人老客户送 钻石用户充值28u 升级钻石特惠并且加28分 永久不消失 熟人老客户降价给 至尊用户充值58u 升级至尊特惠并且加58分 永不消失 由低到高,越高最优惠,可以拉群 @lovesadu

7 Aug 2026, 05:39 UTC959 views2 reactionsread 2 September 2026
Photo

文全补齐猎魔全网涨价 依然保持最优质量、最快速度 人在一分钟一单!人在一分钟一单! 文字全户 12u (丝滑出单) 公网补齐 10u (可带排除 任意17位) 公网猎魔 10u (可带任意排除) 老线路、高质量、超丝滑 大库户籍地2u 95%均为实时户籍地 24h秒单 机器人空的也可以来试! 大部分机器人空的人工照样出! 秒线破解支百12u 已测试埋雷、有些真支空的也能出! 无视一切未认证、脱库、邮箱、港澳台、异常号、大众名如张三李四等 @lovesadu

❤2

5 Aug 2026, 13:06 UTC475 views2 reactionsread 2 September 2026

机器人已经恢复 黄金用户特权消失的 大家来后台找我补等级 假地价格上涨后会更新钻石等级 补特权联系 @lovesadu 暂时主业务不做假地类 等待价格回调 不妨碍目前机器人照样秒单

❤2

29 Jul 2026, 04:52 UTC631 viewsread 2 September 2026
Photo

今天假地价格狂欢🎉 0.5u 0.5u 0.5u 0.5u 今天假地价格狂欢🎉 0.5u 0.5u 0.5u 0.5u 已更新户籍地出单模式 只需身份证即可出单 简化了出单模式 也是只有身份证不知道名字并且 社工库查询空出名字的不二之选! 机器人 @lovedejiadizhibot 客服 @lovesadu 助理 @kunkundei

27 Jul 2026, 13:24 UTC628 views0 reactionsread 2 September 2026

由于市场近期都在低价 我们决定跟随市场价 明天散单假地址 单头😀.😀😀 发送/start 刷新价格 机器人 @lovedejiadizhibot 秒单 okpay可自助充值最低0.1U也可以充用多少充多少实现不怕多充大家更安心! 各位新/老客户来免费升级黄金用户! 批量更低!批量老板拿屠龙刀来砍我! 客服 @lovesadu

19 Jul 2026, 13:55 UTC≈1,500 views2 reactionsread 2 September 2026
Photo

‼️bot更新大通知‼️ 我们删去了繁琐的批量模式 /gh /jdz /hjd 可直接批量 目前功能有 /gh 单公网头 可直接批量 /jdz plc版本公网头 可直接批量 /hjd 户籍地 可直接批量 /pjzd 户籍地+公网头拼接plc /pjzf 户籍地+公网头拼接正反 /gwhjd 公网实时户籍地 以上均为秒线 自助出单非人工 批量老板来问价超低!可开bot! 支持可以okpay充值也可以人工充值 人工支持微信 okpay 支付宝 客服 @lovesadu @kunkundei 老客户熟人直接来升级黄金用户 使用前先看置顶使用须知!! 使用前先看置顶使用须知!! 使用前先看置顶使用须知!! 假地/户籍地/拼接bot @lovedejiadizhibot 假地址/单头/拼接 开机时间 07:30-19:30 户籍地 开机时间24h

❤2

12 Jul 2026, 11:33 UTC807 views1 reactionsread 2 September 2026
Photo

bot使用须知! 新店开业 大家多多照顾 依旧人工充分有神秘福利 人工充值联系 @lovesadu 假地/拼接/正反/户籍地机器人 @lovedejiadizhibot

👎1

Showing the 12 most recent of 16 posts we hold for @love_5213140. 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 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 11 September 2026 — this entry's latest reading, not the date you are reading this.

“love me” (@love_5213140), 484 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/love_5213140.

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.