나선 /
custom 53954482377651826334❤1

Channel
@mootda
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry
19,801subscribers
+203 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001389242941 |
|---|---|
| Type | Channel |
| Username | @mootda |
| Description | (방장한테) 묻지도 따지지도 않는 방 은덕베풀기 : https://litt.ly/mootda Boost : https://t.me/mootda?boost |
| Created | 21 July 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/mootda |
Politics & activism — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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 the other topics.
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.
Posts published here appear in near-verbatim form on 9 other registered channels. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @stoner8740/177126 Nov 2026, 02:19 UTC | @mootda/96382 · this entry6 Nov 2026, 02:22 UTC | 1.00 | 4 minutes |
| @mootda/96543 · this entry9 Nov 2026, 08:51 UTC | @stoner8740/177419 Nov 2026, 08:52 UTC | 1.00 | 72 seconds |
| @stoner8740/1776110 Nov 2026, 02:37 UTC | @mootda/96591 · this entry10 Nov 2026, 02:38 UTC | 1.00 | under a minute |
| @hedgehara/494236 Nov 2026, 08:33 UTC | @mootda/96419 · this entry6 Nov 2026, 08:39 UTC | 1.00 | 6 minutes |
| @umbrellaresearch/4178919 Aug 2026, 05:11 UTC | @mootda/92911 · this entry19 Aug 2026, 05:13 UTC | 1.00 | 3 minutes |
| @mootda/96436 · this entry6 Nov 2026, 23:48 UTC | @umbrellaresearch/431727 Nov 2026, 02:20 UTC | 1.00 | 2.5 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @pharmbiohana | 10 (8/8 hand-verifiable sample passed) | 1.00 | 25 minutes | even |
| @stoner8740 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 72 seconds | @stoner8740 (3–2) |
| @Ten_level | 15 (8/8 hand-verifiable sample passed) | 1.00 | 5 minutes | @Ten_level (12–3) |
| @hedgehara | 8 (8/8 hand-verifiable sample passed) | 1.00 | 28 minutes | @hedgehara (6–2) |
| @umbrellaresearch | 5 (5/5 hand-verifiable sample passed) | 1.00 | 8 minutes | this entry (3–2) |
| @insidertracking | 7 (7/7 hand-verifiable sample passed) | 1.00 | 2 minutes | @insidertracking (6–1) |
| @Yeouido_Lab | 8 (8/8 hand-verifiable sample passed) | 1.00 | 6 minutes | @Yeouido_Lab (6–2) |
| @hogniel | 11 (8/8 hand-verifiable sample passed) | 1.00 | 22 minutes | this entry (6–5) |
| @bbong_tta | 5 (5/5 hand-verifiable sample passed) | 1.00 | 23 minutes | this entry (3–2) |
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. 9 of the 9 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 213 comparable posts for this entry, running 6 August 2026 to 10 November 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.
Recorded under the keys clone_copy · clone_mutual, last confirmed 11 November 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 21:21 | 19,801 | +15 |
| 9 Nov 2026, 09:45 | 19,786 | +10 |
| 8 Nov 2026, 03:58 | 19,776 | +6 |
| 6 Nov 2026, 21:05 | 19,770 | +42 |
| 5 Nov 2026, 21:56 | 19,728 | +12 |
| 4 Nov 2026, 23:19 | 19,716 | +9 |
| 4 Nov 2026, 02:10 | 19,707 | +10 |
| 2 Nov 2026, 23:19 | 19,697 | +18 |
| 1 Nov 2026, 23:16 | 19,679 | -5 |
| 1 Nov 2026, 02:49 | 19,684 | -2 |
| 31 Oct 2026, 01:37 | 19,686 | +5 |
| 30 Oct 2026, 00:59 | 19,681 | +22 |
| 28 Oct 2026, 23:17 | 19,659 | -10 |
| 27 Oct 2026, 18:51 | 19,669 | -4 |
| 26 Oct 2026, 19:57 | 19,673 | +2 |
| 25 Oct 2026, 19:47 | 19,671 | -2 |
| 24 Oct 2026, 18:40 | 19,673 | -5 |
| 22 Oct 2026, 14:00 | 19,678 | -1 |
| 20 Oct 2026, 05:20 | 19,679 | -11 |
| 19 Oct 2026, 07:20 | 19,690 | first reading |
879 posts held, back to 6 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 74 pages of 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. It is computed over the 220 of 264 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 November 2026 |
|---|---|
| Posts held | 879 (6 August 2026 – 11 November 2026) |
| Views total | 655,141 |
| Reactions total | 3,677 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 03:42 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.
Lifetime counters from Telegram’s own channel header, read 11 November 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.
Measured directly from 21 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
15,514 reactions across 733 posts, in 42 distinct kinds. The most used accounts for 19.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 3,067 | 19.8% | |
| ❤ | 1,958 | 12.6% | |
| 💩 | 1,123 | 7.24% | |
| 🤬 | 1,080 | 6.96% | |
| 🤮 | 1,019 | 6.57% | |
| 🤣 | 1,001 | 6.45% | |
| 😁 | 953 | 6.14% | |
| 🖕 | 903 | 5.82% | |
| 🥰 | 608 | 3.92% | |
| 🔥 | 558 | 3.60% | |
| custom 5395448237765182633 | 553 | 3.56% | |
| 💯 | 508 | 3.27% | |
| 👏 | 299 | 1.93% | |
| 😱 | 250 | 1.61% | |
| 😢 | 207 | 1.33% | |
| 😭 | 206 | 1.33% | |
| 🙏 | 198 | 1.28% | |
| 👎 | 186 | 1.20% | |
| custom 5334826161656572009 | 175 | 1.13% | |
| 🤪 | 116 | 0.748% | |
| 22 further kinds | 546 | 3.52% |
Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 772 of the 879 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 15,736 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 879 most recent posts we hold, published 6 August 2026 to 11 November 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @mootda. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 879 most recent posts we hold for this entry, published 6 August 2026 to 11 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Telegram’s own ‘edited’ marker: 18 of 264 posts held from the last 30 days (6.82%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
나선 /
custom 53954482377651826334❤1
└ 코스닥 개떡락하면서 핸들 떼고 자율주행중인데 여기서 4프로 오른다 한들 안전운행이 될리가 없습니다.
👌6👍3
내일 옵션 만기인거 아시죠? 안전 운전들 하세요
❤4custom 53348261616565720091
💻 삼성전자, AMD와 차세대 반도체 테스트 인프라 협력 https://www.yna.co.kr/view/AKR20261111089400003?input=1195m 삼성전자가 AMD의 최신 서버용 프로세서와 자사 메모리·스토리지 제품을 결합해 차세대 반도체 제조 테스트 인프라 고도화에 나섭니다. 📌 AMD 6세대 에픽 프로세서, 삼성 메모리와 결합 AMD가 6세대 EPYC Embedded 9006 시리즈를 공개하며 삼성전자와의 협력 구성 소개 삼성전자의 DDR5 RDIMM·MRDIMM, PCIe 6.0 SSD, CXL 메모리 확장 모듈 적용 차세대 메모리와 고속 입출력 장치의 성능 검증을 위한 테스트 인프라 구축 추진 📌 최대 256코어, 반도체 검사 처리량 확대 AMD 신형 프로세서는 최대 256코어, PCIe 6.0 및 CXL …
❤1
코어위브 +16.85%
❤3
└ 박주민 내란선동죄인데 민주파출소에 신고하면 되나요?
👏15❤2👎1
전쟁? 내란범이 요기잉네 ㅋ https://imnews.imbc.com/news/2026/politics/article/6864780_36912.html
💩17
└ 근데 생각해보면 보수가 집권하지 못한다면 문재인이 돌아오는게 그나마 베스트 케이스임 ㅋㅋㅋㅋㅋ
😱22🤮10custom 53348261616565720096🖕1🤣1
다쉬~ 출뫄할꽈요~?
🖕19🤡10
이 기준으로 개헌되면 웃을 사람 1명 문재인 "훠훠~ 다시 출마할까요?~"
❤2🤣1
오늘 국장 상승은 인간적으로 클론까지 동원해서 기도한 내덕이다. ㅇㅈ?
👍15🥰4💯1🔥1🤣1
└ 바로삼 이라고 사명을 지었으면 오늘 300% 오름.
❤5👍2🤣2
Showing the 12 most recent of 879 posts we hold for @mootda. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 58 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
Republishes
Channels on the register whose posts this channel has forwarded.
Republishes 79 registered channels. The 48 listed are the ones this channel has forwarded most; the rest are counted here but not each listed.
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.
Named by 7 registered channels — 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 9 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“묻따방 🐕” (@mootda), 19,801 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/mootda.
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.