Telegram RegisterThe public register of Telegram
Telegram profile photo for 갸루궈코

Channel

갸루궈코

@tangtangbox

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

2,635subscribers

-26 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001726696456
TypeChannel
Username@tangtangbox
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/tangtangbox

Topic

Other / unclassifiable — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 76% 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.

Growth

2,6352,6692,6527 August 2026 — 2,661 subscribers8 August 2026 — 2,660 subscribers10 August 2026 — 2,661 subscribers17 August 2026 — 2,665 subscribers21 August 2026 — 2,656 subscribers24 August 2026 — 2,659 subscribers27 August 2026 — 2,663 subscribers30 August 2026 — 2,666 subscribers2 September 2026 — 2,667 subscribers6 September 2026 — 2,669 subscribers11 September 2026 — 2,650 subscribers15 September 2026 — 2,643 subscribers19 September 2026 — 2,635 subscribers7 August 202619 September 2026
13 measurements spanning 43 days, net -26. 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 2,630–2,674 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 08:592,635-8
15 Sept 2026, 05:182,643-7
11 Sept 2026, 13:362,650-19
6 Sept 2026, 20:182,669+2
2 Sept 2026, 07:332,667+1
30 Aug 2026, 10:372,666+3
27 Aug 2026, 17:242,663+4
24 Aug 2026, 11:582,659+3
21 Aug 2026, 01:282,656-9
17 Aug 2026, 16:052,665+4
10 Aug 2026, 16:022,661+1
8 Aug 2026, 01:472,660-1
7 Aug 2026, 01:482,661first reading

Engagement

25 posts held, back to 31 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 25 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

29 reactions across 14 posts, in 4 distinct kinds. The most used accounts for 51.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤡1551.7%
1034.5%
👍310.3%
🤔13.45%

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 14 of the 25 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 29 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 25 most recent posts we hold, published 31 July 2026 to 7 August 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

7 Aug 2026, 11:39 UTC223 views2 reactionsread 7 August 2026

담주에 메모리 다 팔고 마음이 편해지려고했는데 롤리랄이 코끼리식 매수했대서 좀 더 홀딩해볼까 고민되어요

🤡2

7 Aug 2026, 11:12 UTC281 views1 reactionsread 7 August 2026

아는 형이 한국에 아파트 살바에 미국 부동산 사서 월세받고 한국은 그돈으로 월세 거주 하는게 낫다라고 했는데 확실히 그런거같긴해

🤡1

7 Aug 2026, 07:59 UTC380 viewsread 7 August 2026
Photo

이래서 이랬구나 (1) 정당하게 쉬려고 흡연자가 되는거구나

6 Aug 2026, 15:33 UTC557 views2 reactionsread 7 August 2026

택시아저씨가 나 불쌍해보인다고 1달러 깍아줌 ;; 개꿀

2

6 Aug 2026, 04:05 UTC575 views1 reactionsread 7 August 2026

집이 시원한데 더위먹은 것처럼 기운이 없음 왤까

🤡1

6 Aug 2026, 00:31 UTC593 views1 reactionsread 7 August 2026

모두가 이제 지쳤어 SK하이닉스, 삼성전자 우리 이제 새로운 사랑으 찾아 떠나자

🤡1

5 Aug 2026, 11:29 UTC611 views5 reactionsread 7 August 2026

'고점'을 내 원금으로 생각해서 마음이 힘들다면, '저점'을 내 원금으로 생각하는게 어떨까요? 매일 행복할거에요. 발상의 전환 발상의 전환

👍3🤡2

5 Aug 2026, 04:05 UTC641 views1 reactionsread 7 August 2026

우라늄하고 구리 ETF 매력적으로 보여요 살 돈은 없고요

🤡1

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

Forward network

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.

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

“갸루궈코” (@tangtangbox), 2,635 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/tangtangbox.

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.