0xf2915d1e3C1B0c769d0c7562243F1c1f63392222

Channel
永恒牛市
@yonghengniu
On this record: Growth · Engagement · Posts · Citations · Cite this entry
62subscribers
-2 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001779955714 |
|---|---|
| Type | Channel |
| Username | @yonghengniu |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/yonghengniu |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 04:00 | 62 | -1 |
| 3 Sept 2026, 15:02 | 63 | -1 |
| 12 Aug 2026, 06:00 | 64 | no change |
| 12 Aug 2026, 05:46 | 64 | first reading |
Engagement
20 posts held, back to 20 November 2025 — 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.
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 10 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
0x0339f5459fc690ac85f1782e15782a151b4a2222
0x0339f5459fc690ac85f1782e15782a151b4a9e22
0xf2915d1e3C1B0c769d0c756Ec43F1c1f63392222
0xf2915d1e3C1B0c769d0c756Ec43F1c1f6c992222
0x2a846aaaf896ef393ccb76398c1d96e222374444
0x9dd34e127e5198bcf4ebb400902e772222224444
0xd85c318522220fb40aaa9e2222da23c21f822d46
0xd85c318522220fb40aaa9e2222da23222f822d46
0x9dd34e127e5198bcf4ebb400902222fd22224444
0xd85c318522220fb40aaa9e2222da23c21f822d46
0xd85c318522220fb40aaa9e2fc4da23c21f822d46
Showing the 12 most recent of 20 posts we hold for @yonghengniu. 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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“永恒牛市” (@yonghengniu), 62 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/yonghengniu.
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.