여행 마지막 일정 동물원 왔어요 내일 귀국이라니..
custom 533238033240033106529custom 58256624459469347237custom 59945526460636253764custom 54476338083984995761

Channel
@Thoughts_BFox
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
14,665subscribers
+55 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002556510058 |
|---|---|
| Type | Channel |
| Username | @Thoughts_BFox |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/Thoughts_BFox |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 15:55 | 14,665 | -1 |
| 3 Sept 2026, 18:59 | 14,666 | +20 |
| 2 Sept 2026, 08:04 | 14,646 | -6 |
| 1 Sept 2026, 04:43 | 14,652 | +5 |
| 31 Aug 2026, 02:48 | 14,647 | -5 |
| 30 Aug 2026, 05:46 | 14,652 | -2 |
| 29 Aug 2026, 03:53 | 14,654 | -6 |
| 28 Aug 2026, 04:13 | 14,660 | -3 |
| 27 Aug 2026, 06:33 | 14,663 | +9 |
| 26 Aug 2026, 07:42 | 14,654 | -6 |
| 25 Aug 2026, 04:12 | 14,660 | -5 |
| 23 Aug 2026, 22:35 | 14,665 | -9 |
| 22 Aug 2026, 08:06 | 14,674 | -4 |
| 20 Aug 2026, 21:12 | 14,678 | -3 |
| 18 Aug 2026, 19:22 | 14,681 | -8 |
| 17 Aug 2026, 18:42 | 14,689 | -7 |
| 16 Aug 2026, 15:13 | 14,696 | +8 |
| 14 Aug 2026, 23:14 | 14,688 | -7 |
| 13 Aug 2026, 18:14 | 14,695 | -7 |
| 12 Aug 2026, 16:33 | 14,702 | first reading |
200 posts held, back to 5 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 51 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 137 of 157 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 200 (5 August 2026 – 2 September 2026) |
| Views total | 638,450 |
| Reactions total | 3,999 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 18:27 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.
Measured directly from 2 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.
4,591 reactions across 156 posts, in 4 distinct kinds. The most used accounts for 43.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5332380332400331065 | 1,983 | 43.2% | |
| custom 5825662445946934723 | 1,213 | 26.4% | |
| custom 5994552646063625376 | 718 | 15.6% | |
| custom 5447633808398499576 | 677 | 14.7% |
Custom emoji. Every row above is a 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 171 of the 200 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 4,800 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 200 most recent posts we hold, published 5 August 2026 to 2 September 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.
여행 마지막 일정 동물원 왔어요 내일 귀국이라니..
custom 533238033240033106529custom 58256624459469347237custom 59945526460636253764custom 54476338083984995761
그래도 올릴건 올려야지 이번주도 꽤나 볼게 많긴해요
custom 533238033240033106521
합병시에 현금 1.14$ + 지분 10% 스타맨 옵티컬 벨류따라 1b = 1.54$ 2b = 1.94$ 정도 측정됨.
custom 53323803324003310659
고프로 이거 이틀동안 왜오르나 했더니
custom 599455264606362537612
https://youtu.be/Z5gjHa53sR0?si=rhvK8L8YZ2WBC6RX KB증권에서 영상이 하나 나왔는데 ㅋㅋㅋㅋ 저한테는 연락온거 따로 없었는데, KB에서 따로 만들었나봐요. 30분넘는 영상인데 절반이 제이야기만 하네요 ㅋㅋㅋㅋㅋㅋ.. 연락하시지 참석 해드렸을건데
custom 533238033240033106541
생일축하해주신분들 다들 너무 감사합니다. 싱가포르 두번째 오지만 너무 좋네요.. 진짜 여기서 살고 싶다 그럴려면 잘 쉬고 돌아가서 또 잘 벌어보겠습니다 ㅎㅎ 진짜 쉬는동안 매매는 안하려고 하고 있어요
custom 5332380332400331065127custom 599455264606362537618custom 582566244594693472315
https://m.blog.naver.com/hodolry/224359820120 회원가입도 없고 공짜로 사용가능한 사이트하나 소개 기능이나 소개는 블로그 들어가보시면 있어요 (저는 저분이 누군지 모름 광고 아님)
custom 599455264606362537630custom 53323803324003310654
저는 오늘부터 목요일까지 휴가입니다. 싱가포르로 다녀올 예정이에요. 짧지만 잘 쉬다 오겠습니다!
custom 533238033240033106569custom 58256624459469347232custom 59945526460636253762
Photo, posted without a caption
custom 53323803324003310659custom 58256624459469347233custom 59945526460636253762
주말동안 생각해보고 글 올릴게요. 대충보고 쓴거라..
custom 533238033240033106530
아 근데 중간선거 전에 금리인상 하려면 지금밖에 없네..
custom 582566244594693472323
그렇다고 금리를 올리진 못할거라고 일단 생각합니다.
custom 599455264606362537628
Showing the 12 most recent of 200 posts we hold for @Thoughts_BFox. 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.
@Thoughts_BFox edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
Named by 6 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.
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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“생각 정리하는 방” (@Thoughts_BFox), 14,665 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/Thoughts_BFox.
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.