2 measurements spanning 4 days. 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 13–15 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 01:46
14
no change
7 Aug 2026, 21:51
14
first reading
Engagement
20 posts held, back to 14 August 2023 — 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 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 20 posts for this entry, the most recent from 4 January 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
≈3,180
Links
≈3,160
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
1 reaction across 1 post, in 1 kind.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
1
100.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 1 of the 20 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 14 August 2023 to 4 January 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🥳#Binance công bố dự án thứ 43 trên Binance Launchpool -
@XAI_GAMES
XAI (XAI)
🥳Anh em sẽ có thể đặt cược BNB, FDUSD và TUSD vào các nhóm riêng biệt để nuôi mã thông báo XAI trong bốn ngày, với quá trình farming bắt đầu từ 2024-01-05 07:00 (giờ VN).
🚨IDO sắp diễn ra 🚨
🚀@ai_malls sẽ tổ chức IDO vào 27/10/2023 tại các sàn Kommunitas, BSC Station, Kingdomstarter.
LichGoiVon.com | Kênh Telegram | Nhóm thảo luận | Twitter | Đăng ký sàn giao dịch
!IDO sắp diễn ra !
🚀Lamas Finance sẽ tổ chức IKO vào ngày 25-31/10/2023
The IKO sẽ diễn ra tại Kommunitas.
📷 Price: $0.3 / LMF
LichGoiVon.com | Kênh Telegram | Nhóm thảo luận | Twitter | Đăng ký sàn giao dịch
⭐️IDO sắp diễn ra ⭐️
🚀Chappyz sẽ tổ chức IDO tại Chain GPT vào 26/10/2023
🚀Chappyz IDO tổ chức tại Poolz vào 01/11/2023
🚀Chappyz sẽ tổ chức IDO tại Seedify vào 02/11/2023
LichGoiVon.com | Kênh Telegram | Nhóm thảo luận | Twitter | Đăng ký sàn giao dịch
🚨IEO sắp diễn ra 🚨
🚀@PK_Alterna_EN sẽ tổ chức IEO tại http://Gate.io vào ngày 09-10-2023.
LichGoiVon.com | Kênh Telegram | Nhóm thảo luận | Twitter | Đăng ký sàn giao dịch
🚀IDO sắp diễn ra 🚀
🚨EDriveToken sẽ tổ chức bán công khai vào ngày 04-1-2023 tại Kommunitas.
👉Anh em lưu lại ngày nha.
#IDO #Lichgoivon #EDrive
LichGoiVon.com | Kênh Telegram | Nhóm thảo luận | Twitter | Đăng ký sàn giao dịch
🚀IDO sắp diễn ra 🚀
🚀@tezosdomains sẽ tổ chức 25-09-2023 tại TrustSwap.
#IDO #ICO #IDOdar #Tezosdomains
LichGoiVon.com | Kênh Telegram | Nhóm thảo luận | Twitter | Đăng ký sàn giao dịch
🚀IDO sắp diễn ra 🚀
🚀@DinoWars_Game IDO sẽ được tổ chức tại @trustfiorg
⭐️Khi nào: 17-09-2023
LichGoiVon.com | Kênh Telegram | Nhóm thảo luận | Twitter | Đăng ký sàn giao dịch
⭐️IDO sắp diễn ra ⭐️
🚀@nebuladex
IDO mở bán vào ngày 14-09-2023 tại http://nebuladex.io/ido
LichGoiVon.com | Kênh Telegram | Nhóm thảo luận | Twitter | Đăng ký sàn giao dịch
🚀Anh em đã sẵn sàng cho IDO sắp diễn ra tại Seedify?
@soil_farm x @SeedifyFund
😍Theo dõi lịch IDO ngay tại #Lichgoivon
LichGoiVon.com | Kênh Telegram | Nhóm thảo luận | Twitter | Đăng ký sàn giao dịch
⭐️IDO sắp diễn ra ⭐️
🚀Hibiki Run sẽ tổ chức IDO tại Spores ngày 18-09-2023
🚀Hibiki Run sẽ mở bán Flash Sale tại BitMart ngày 18-09 -2023
Signed Stellalovecrypto
Showing the 12 most recent of 20 posts we hold for @lichgoivon. 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
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.
Handles this channel named that no longer answer
Dead references
7
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
7
vacant every time we have ever looked
@lichgoivon named 7 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@another1_io named in 1 post, 13 August 2026 – 13 August 2026
@bwecorporation named in 1 post, 13 August 2026 – 13 August 2026
@darkverse42 named in 1 post, 13 August 2026 – 13 August 2026
@soil_farm named in 1 post, 13 August 2026 – 13 August 2026
@trustfiorg named in 1 post, 13 August 2026 – 13 August 2026
@xai_games named in 1 post, 13 August 2026 – 13 August 2026
@zetablockchain named in 1 post, 13 August 2026 – 13 August 2026
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 12 August 2026 — this
entry's latest reading, not the date you are reading this.
“LichGoiVon.com” (@lichgoivon), 14 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/lichgoivon.
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.