Telegram RegisterThe public register of Telegram

Channel

Chứng khoán Việt Nam

@chungkhoanvietnammoon

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Cite this entry

3,431subscribers

-4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001230017330
TypeChannel
Username@chungkhoanvietnammoon
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/chungkhoanvietnammoon

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 41% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@chungkhoanvietnammoon/3401 · this entry27 May 2026, 07:08 UTC@hocchungkhoancungViet/624927 May 2026, 07:09 UTC1.0072 seconds
@chungkhoanvietnammoon/3407 · this entry16 Jun 2026, 12:17 UTC@hocchungkhoancungViet/625416 Jun 2026, 12:17 UTC1.00under a minute
@chungkhoanvietnammoon/3408 · this entry22 Jun 2026, 01:32 UTC@hocchungkhoancungViet/625522 Jun 2026, 01:35 UTC1.004 minutes
@chungkhoanvietnammoon/3413 · this entry13 Jul 2026, 05:31 UTC@hocchungkhoancungViet/626113 Jul 2026, 05:33 UTC1.002 minutes
@chungkhoanvietnammoon/3414 · this entry14 Jul 2026, 00:37 UTC@hocchungkhoancungViet/626214 Jul 2026, 00:45 UTC1.008 minutes
@chungkhoanvietnammoon/3417 · this entry24 Jul 2026, 00:35 UTC@hocchungkhoancungViet/626524 Jul 2026, 02:46 UTC1.002.2 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@hocchungkhoancungViet8 (8/8 hand-verifiable sample passed)1.002 minutesthis entry (80)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 8 comparable posts for this entry, running 27 May 2026 to 30 July 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @chungkhoanvietnammoon — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

3,4313,4353,4337 August 2026 — 3,435 subscribers7 August 2026 — 3,435 subscribers7 August 2026 — 3,434 subscribers10 August 2026 — 3,431 subscribers7 August 202610 August 2026
4 measurements spanning 4 days, net -4. 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 3,430–3,436 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 21:233,431-3
7 Aug 2026, 11:373,434-1
7 Aug 2026, 01:303,435no change
7 Aug 2026, 01:243,435first reading

Engagement

20 posts held, back to 27 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
18.4%
avg views ÷ 3,431 subscribers
Avg views / post
632
7 posts measured
Reaction rate
0.66%
reactions ÷ views · ER floor
Posts in window
7
of 20 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 5 of 7 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 30 July 2026
Posts held20 (27 May 202630 July 2026)
Views total4,424
Reactions total21
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:14 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

61 reactions across 16 posts, in 5 distinct kinds. The most used accounts for 72.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4472.1%
👍813.1%
😁46.56%
🥰34.92%
🤝23.28%

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 17 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 61reactions 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 27 May 2026 to 30 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

30 Jul 2026, 14:06 UTC442 views4 reactionsread 7 August 2026
Photo

Thế hệ tan vỡ ở Hàn Quốc. Chỉ trong vài tuần, chỉ số ck KOSPI của HQ lao dốc 40% từ đỉnh, có những phiên giảm tới 11%, vốn hóa thị trường bốc hơi hơn 2.000 tỷ USD. Hàng trăm nghìn tài khoản margin bị call, riêng hơn 360.000 tài khoản đã bị thanh lý hoàn toàn, phần lớn thuộc về nhà đầu tư dưới 35 tuổi. Khi lương không đủ mua nhà, người ta mua hy vọng bằng đòn bẩy. Thị trường thì chỉ mất vài phiên để thanh lý cả hai

3👍1

30 Jul 2026, 00:54 UTC481 viewsread 7 August 2026
Photo

Chỉ số chứng khoán Hàn Quốc đã giảm 40% từ đỉnh. Bên đó dân chơi chứng khoán khá liều lĩnh

28 Jul 2026, 02:33 UTC501 views1 reactionsread 7 August 2026

Chỉ số Kospi của Hàn đã phải ngừng giao dịch vì giảm 8%, không biết anh em VNindex hôm nay sẽ thế nào đây 😌

1

27 Jul 2026, 02:09 UTC575 views3 reactionsread 7 August 2026

Chính thức: Ngân hàng LPBank công bố bà Phạm Thu Hương, Phó Chủ tịch HĐQT Vingroup, hiện sở hữu 148,3 triệu cổ phiếu, tương đương 4,965% số lượng cổ phiếu lưu hành. Cùng với ông Phạm Nhật Vượng, hai cổ đông hiện nắm giữ tổng cộng 294,5 triệu cổ phiếu, tương đương 9,86% vốn điều lệ của ngân hàng. >>> Theo ae, sắp tới HĐQT LPBank có thay đổi gì ko?

3

24 Jul 2026, 00:35 UTC784 views9 reactionsread 7 August 2026

Trong Uptrend, bạn càng biết nhiều, càng nhảy nhót nhiều, bạn càng ăn ít. Trong Downtrend, bạn càng tỏ vẻ mình giỏi, càng đi ngược đám đông, càng tham lam khi người khác sợ hãi… thì bạn càng lỗ nặng. Việc đơn giản là Uptrend chọn cổ phiếu tốt và ngồi yên. Downtrend cầm tiền và bớt quan tâm thị trường lại. Tiền bạn kiếm được là do UPTREND, không phải do bạn giỏi đâu. “Ngu và Lỳ” – Thực ra là thuận theo xu hướng mà

5🥰3👍1

22 Jul 2026, 11:55 UTC759 viewsread 7 August 2026

Market vẫn xả tiếp đấy nhé ace, vừa tin chiến tranh, lãi suất + kiểm tra các doanh nghiệp

20 Jul 2026, 09:30 UTC882 views4 reactionsread 7 August 2026
Photo

Đây là lý do mình vẫn cho ae chờ. Cứ nằm vùng chờ thời cho an tâm nhé ae

4

14 Jul 2026, 00:37 UTC≈1,120 views6 reactionsread 7 August 2026

Đợt này lãi suất ở VN khá cao, Fed cũng chuẩn bị nâng lãi suất vài lần tiếp theo nên tớ chờ Vnindex về 1500-1600 các cậu ạ

👍6

13 Jul 2026, 05:31 UTC≈1,090 views5 reactionsread 7 August 2026

🔴 Chỉ số KOSPI của Hàn Quốc giảm xuống 6800 điểm, giảm 9,07% trong ngày. SK Hynix giảm 14,5%, trong khi Samsung Electronics giảm 11%.

5

10 Jul 2026, 09:40 UTC≈1,150 views5 reactionsread 7 August 2026
Photo

Mình đang chờ xem nó giảm về bao nhiêu mới cho ace nhặt hàng

5

24 Jun 2026, 13:56 UTC≈1,380 views3 reactionsread 7 August 2026
Photo

Bitcoin mình thấy view giảm tiếp, tham khảo thôi nha

3

24 Jun 2026, 03:35 UTC≈1,210 viewsread 7 August 2026
Photo

Vnindex tung nóc 87 điểm nhưng lạ lắm 😂

Showing the 12 most recent of 20 posts we hold for @chungkhoanvietnammoon. 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.

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

“Chứng khoán Việt Nam” (@chungkhoanvietnammoon), 3,431 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/chungkhoanvietnammoon.

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.