Channel
@mastersim77
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
492subscribers
-1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004319873330 |
|---|---|
| Type | Channel |
| Username | @mastersim77 |
| Created | Between 1 June 2026 and 7 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 8 August 2026 |
| On Telegram | t.me/mastersim77 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 16:22 | 492 | -1 |
| 8 Aug 2026, 09:05 | 493 | first reading |
20 posts held, back to 7 August 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 20 (7 August 2026 – 8 August 2026) |
| Views total | 687 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 09:05 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.
1. winevo 입플 6+4 +2만이체 2. krvip 입플 6+6 +2만이체 3. skwin 입플 6+6 +2만이체 4. gamekor 입플 6+4 +2만이체 5. wonwin 입플 6+6 +2만이체 6. kcwin 입플 6+4 +2만이체 7. krwin 입플 3+3 +1만이체 8. ktwin 입플 6+4 +2만이체 9. betkrw 입플 3+3 +1만이체 가입후 금액이 같거나크게 입금하시면 따로 현금 이체해드립니다. 한사이트마다 개당지급입니다. 미성년자 가능합니다. 문의: @Yunjung_888
08월 10일 💗미리 문의 예약 가능합니다. 지인 친구분들 데려오시면 토스비 + 보너스 드리겠습니다. 금일 하루도 고생 많으셨습니다. ❤️이벤트.특가로 토스실장 개통실장 최고우대 해드립니다❤️ 💗예약 가능수량 : 12개 정심 마감입니당 💗 @Mastersim7 금일 하루 고생하셨습니다! 금일 2개 급건 보너수나가요
맞홍
💬카카오톡 실계정 매입💬 💵단가:1️⃣0️⃣0️⃣0️⃣0️⃣0️⃣💵 🔺이메일 등록일수 1년이상 🔺친구수 100명 이상 🔺채팅내역 다수 보유(광고채팅 불가) 🔺전화번호 🔺카카오톡 비밀번호 정지 피해 일절없습니다 다시 사용가능합니다‼️ 💙💙@Ddo_chi0 💙💙@Ddo_chi1 1ㅎ
펭귄 매입 단가표⭐️⭐️⭐️ 당근마켓⭐️ 36.5도💗💗💗💗💗원 37도 💗💗💗💗💗원 38도 💗💗💗💗💗원 ➖➖➖➖➖➖➖➖ 번개장터⭐️ 기존계정(사용 하시던 계정) 💗💗💗💗💗원 ➖➖➖➖➖➖➖➖ 중고나라⭐️🌟 앱+카페 연동계정 💗💗💗💗💗원 ➖➖➖➖➖➖➖➖ 📌첫거래는 케어후 정산 📌거래처 문의 환영 💗💗 @oooo99088 💗💗 https://t.me/oooo9908
맞홍
맞홍
🧋단가표🧋 ⭐️신규 😃🥹☺️☺️☺️ ⭐️36.5도😄☺️☺️☺️☺️ ⭐️37.0도😁🥹☺️☺️☺️ ⭐️38.0도😆🥹☺️☺️☺️ ⭐️39.0도🥹🥹☺️☺️☺️ ⭐️40도 이상은 조율 ⭐️번개장터 100일 이상 😃☺️☺️☺️☺️ 그뒤일수부터 조율 ⭐️중고나라 앱계정 1.5 ⭐️중고나라 앱+카페 2.0 💗💗@BOKSULEE9 💗💗https://t.me/BOKSULEE
오늘 물건 3개만 하나 당 20만원 바로 매입할게용 급건입니다 연락주세여 2회
08월 10일 💗미리 문의 예약 가능합니다. 지인 친구분들 데려오시면 토스비 + 보너스 드리겠습니다. 금일 하루도 고생 많으셨습니다. ❤️이벤트.특가로 토스실장 개통실장 최고우대 해드립니다❤️ 💗예약 가능수량 : 12개 정심 마감입니당 💗 @Mastersim7 금일 하루 고생하셨습니다! 금일 2개 급건 보너수나가요
08월 07일 💗미리 문의 예약 가능합니다. 지인 친구분들 데려오시면 토스비 + 보너스 드리겠습니다. 금일 하루도 고생 많으셨습니다. 💗예약 가능수량 : 2개 정심 마감입니당 💗 @Mastersim7 금일 하루 고생하셨습니다! 보너스 나가요 지금 2개 급건
맞홍
Showing the 12 most recent of 20 posts we hold for @mastersim77. 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.
Citation-graph rank — 405,628 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
@mastersim77 named 1 handle 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“개통 마스터 채널” (@mastersim77), 492 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/mastersim77.
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.