Telegram RegisterThe public register of Telegram
Telegram profile photo for BTCparser1

Channel

BTCparser1

@BTCparser1

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

3,009subscribers

+10 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001278195336
TypeChannel
Username@BTCparser1
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/BTCparser1

Topic

Crypto & trading — 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 56% 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,9883,0163,0026 August 2026 — 2,999 subscribers7 August 2026 — 2,998 subscribers10 August 2026 — 3,002 subscribers14 August 2026 — 2,998 subscribers17 August 2026 — 2,997 subscribers20 August 2026 — 2,992 subscribers24 August 2026 — 2,988 subscribers31 August 2026 — 2,993 subscribers3 September 2026 — 2,992 subscribers8 September 2026 — 3,016 subscribers12 September 2026 — 3,012 subscribers16 September 2026 — 3,009 subscribers3,0096 August 202616 September 2026
12 measurements spanning 41 days, net +10. 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,984–3,020 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 06:573,009-3
12 Sept 2026, 18:383,012-4
8 Sept 2026, 10:363,016+24
3 Sept 2026, 10:442,992-1
31 Aug 2026, 00:122,993+5
24 Aug 2026, 09:592,988-4
20 Aug 2026, 09:272,992-5
17 Aug 2026, 12:072,997-1
14 Aug 2026, 00:352,998-4
10 Aug 2026, 16:373,002+4
7 Aug 2026, 06:172,998-1
6 Aug 2026, 13:212,999first reading

Engagement

43 posts held, back to 3 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 3 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 43 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

52 reactions across 41 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥52100.0%

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

Measured over the 43 most recent posts we hold, published 3 August 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, 19:17 UTC80 viewsread 8 August 2026

2026-08-07 19:17:25.668 1HwXorRhy4jbPVeCBB8MU885JGxnBejerg created 15.11.2013 -10.00000000 block:961482

7 Aug 2026, 19:05 UTC89 viewsread 8 August 2026

2026-08-07 19:05:59.822 1GeApEU6bnmzH3pctLSNK5dT6geaZRG9sE created 03.04.2017 -0.00000547 block:961479

7 Aug 2026, 17:20 UTC117 views1 reactionsread 8 August 2026

2026-08-07 17:21:13.551 1FX4cfJ827VgP5j1Pk4tJcu9kLbnTXHkN9 created 07.12.2016 -21.99011182 block:961466

🔥1

7 Aug 2026, 06:41 UTC171 views1 reactionsread 8 August 2026

2026-08-07 06:41:57.954 1N6B6oQC5SWUsjaYBHRbuVarFVubk2nZVF created 27.01.2014 -22.83770485 block:961384

🔥1

7 Aug 2026, 06:41 UTC167 views1 reactionsread 8 August 2026

2026-08-07 06:41:53.735 17ceUqFhRuDsGE7pyGPdqL51HbPSbtcbKu created 02.02.2014 -19.70839875 block:961384

🔥1

7 Aug 2026, 06:41 UTC165 views1 reactionsread 8 August 2026

2026-08-07 06:41:49.532 12UWZjTJ9q6aijSfAZMaQ2qEvJJEX3tLqA created 27.01.2014 -19.49879778 block:961384

🔥1

7 Aug 2026, 05:53 UTC171 views1 reactionsread 8 August 2026

2026-08-07 05:53:33.257 1G2PP56SSsFvUxwNRwPbXMR8z9z6tT7G9u created 03.02.2014 -16.79583759 block:961379

🔥1

7 Aug 2026, 05:28 UTC174 views1 reactionsread 8 August 2026

2026-08-07 05:28:17.939 1kBrFXYSwntMLDySJnwaKEFtE1GBS7mNY created 27.01.2014 -17.09855333 block:961377

🔥1

7 Aug 2026, 05:27 UTC171 views1 reactionsread 8 August 2026

2026-08-07 05:28:14.611 1P3Gc7Xwmk6njx4TyF7RRsume2W2RuzTkZ created 02.02.2014 -32.60479094 block:961377

🔥1

7 Aug 2026, 05:27 UTC165 views1 reactionsread 8 August 2026

2026-08-07 05:28:11.173 1Jgitz4thBh8UsL3cY49VgHUZLJ8Z5f8xi created 02.02.2014 -24.70480547 block:961377

🔥1

7 Aug 2026, 05:27 UTC164 views1 reactionsread 8 August 2026

2026-08-07 05:28:07.720 1E53kwpy5d5RhmJoR94WH5TstRswQmWp1T created 30.01.2014 -16.80984000 block:961377

🔥1

7 Aug 2026, 05:27 UTC161 views1 reactionsread 8 August 2026

2026-08-07 05:28:04.298 1BrT9jGWhwz7f28o4tKfoLdh9QxBUy3Qi6 created 04.02.2014 -15.37800000 block:961377

🔥1

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“BTCparser1” (@BTCparser1), 3,009 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/BTCparser1.

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.