Telegram RegisterThe public register of Telegram
Telegram profile photo for msgETH - Ethereum Transaction Monitor

Channel

msgETH - Ethereum Transaction Monitor

@msgeth

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

928subscribers

-7 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-1002041633495
TypeChannel
Username@msgeth
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live28 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/msgeth

Growth

9289369327 August 2026 — 935 subscribers8 August 2026 — 935 subscribers15 August 2026 — 936 subscribers21 August 2026 — 929 subscribers28 August 2026 — 928 subscribers7 August 202628 August 2026
5 measurements spanning 21 days, net -7. 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 927–937 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 17:24928-1
21 Aug 2026, 10:37929-7
15 Aug 2026, 00:24936+1
8 Aug 2026, 00:50935no change
7 Aug 2026, 13:56935first reading

Engagement

20 posts held, back to 7 August 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
0.253%
avg views ÷ 928 subscribers
Avg views / post
2.4
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held20 (7 August 20268 August 2026)
Views total47
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 00:50 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.

Recent posts

8 Aug 2026, 00:35 UTC2 viewsread 8 August 2026

🟡🟡🟡 Transfer: 298,355,912.693484 DAI From: 0x0000000000000000000000000000000000000000 To: 0xf6e72db5454dd049d0788e411b06cfaf16853042 (Sky: LitePSM USDC A) Block: 25706618 Details #DAIx3

8 Aug 2026, 00:15 UTC2 viewsread 8 August 2026

🔵🔵🔵 Transfer: 300,000,000 USDC From: 0xa188eec8f81263234da3622a406892f3d630f98c To: 0x37305b1cd40574e4c5ce33f8e8306be057fd7341 Block: 25706594 Details #USDCx3

8 Aug 2026, 00:15 UTC2 viewsread 8 August 2026

🔵🔵🔵 Transfer: 300,000,000 USDC From: 0xd0a61f2963622e992e6534bde4d52fd0a89f39e0 To: 0xa188eec8f81263234da3622a406892f3d630f98c Block: 25706594 Details #USDCx3

8 Aug 2026, 00:15 UTC2 viewsread 8 August 2026

🔵🔵🔵 Transfer: 300,000,000 USDC From: 0x688cc76d3b009d805ab6b4d0a1cbd228131b5cbf To: 0xd0a61f2963622e992e6534bde4d52fd0a89f39e0 Block: 25706594 Details #USDCx3

8 Aug 2026, 00:14 UTC2 viewsread 8 August 2026

🔵🔵 Transfer: 179,527,744 USDC From: 0x56957e411ea83a0b4a0689c1fb0d1e5ea0d20149 To: 0x98c23e9d8f34fefb1b7bd6a91b7ff122f4e16f5c (Aave: USDC V3) Block: 25706581 Details #USDCx2

8 Aug 2026, 00:14 UTC2 viewsread 8 August 2026

🔵🔵 Transfer: 179,527,744 USDC From: 0x31173ed183e5a9450c3671018ec4d770c8a8bf18 To: 0x56957e411ea83a0b4a0689c1fb0d1e5ea0d20149 Block: 25706569 Details #USDCx2

8 Aug 2026, 00:14 UTC2 viewsread 8 August 2026

🔵🔵🔵 Transfer: 300,000,000 USDC From: 0x31173ed183e5a9450c3671018ec4d770c8a8bf18 To: 0x688cc76d3b009d805ab6b4d0a1cbd228131b5cbf Block: 25706567 Details #USDCx3

8 Aug 2026, 00:14 UTC2 viewsread 8 August 2026

🔵🔵🔵🔵 Transfer: 479,527,744 USDC From: 0xf1edbf98dda764ec51de3776371f0f7d6f6156a8 To: 0x31173ed183e5a9450c3671018ec4d770c8a8bf18 Block: 25706551 Details #USDCx4

8 Aug 2026, 00:14 UTC2 viewsread 8 August 2026

🟡🟡🟡 Transfer: 300,000,000.000282 DAI From: 0xa188eec8f81263234da3622a406892f3d630f98c To: 0x0000000000000000000000000000000000000000 Block: 25706594 Details #DAIx3

8 Aug 2026, 00:14 UTC2 viewsread 8 August 2026

🟡🟡🟡 Transfer: 300,000,000.000282 DAI From: 0xf6e72db5454dd049d0788e411b06cfaf16853042 (Sky: LitePSM USDC A) To: 0xa188eec8f81263234da3622a406892f3d630f98c Block: 25706594 Details #DAIx3

8 Aug 2026, 00:14 UTC2 viewsread 8 August 2026

🟡🟡🟡🟡 Transfer: 500,000,000 DAI From: 0x60744434d6339a6b27d73d9eda62b6f66a0a04fa To: 0x0000000000000000000000000000000000000000 Block: 25706533 Details #DAIx4

8 Aug 2026, 00:14 UTC2 viewsread 8 August 2026

🟡🟡🟡🟡 Transfer: 500,000,000 DAI From: 0x4b47d7291664beb43e03588e2698e10ba2cd21b3 To: 0x60744434d6339a6b27d73d9eda62b6f66a0a04fa Block: 25706533 Details #DAIx4

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

“msgETH - Ethereum Transaction Monitor” (@msgeth), 928 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/msgeth.

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.