Telegram RegisterThe public register of Telegram
Telegram profile photo for BitContract.cc Official

Channel

BitContract.cc Official

@Bitcontract_cc_official

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

33subscribers

-2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001299768557
TypeChannel
Username@Bitcontract_cc_official
Created12 June 2018 — measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live12 October 2026
Measurements held4
Confirmed unchanged6 times, most recently 12 October 2026
On Telegramt.me/Bitcontract_cc_official

Topic

Marketing & affiliate — 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 30 September 2026 and assigned it the closest of 31 fixed categories, at 42% 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

3335347 August 2026 — 35 subscribers10 August 2026 — 35 subscribers14 August 2026 — 34 subscribers22 August 2026 — 33 subscribers7 August 202622 August 2026
4 measurements spanning 15 days, net -2. 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 33–35 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 18:2733-1
14 Aug 2026, 16:2934-1
10 Aug 2026, 23:1735no change
7 Aug 2026, 20:2535first reading

Engagement

3 posts held, back to 12 June 2018 — 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 page 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 3 posts for this entry, the most recent from 12 June 2018. An engagement rate over an empty window would be a number about nothing.

Recent posts

12 Jun 2018, 17:46 UTC≈3,330 viewsread 10 August 2026

Hello dear investors! Welcome to Bitcontract.cc. A place where you can earn using your Bitcoins😊 Our team has worked hard and long to develop our investment resource. For months, we developed and debugged our software to provide maximum comfort and security for our platform.🤓 Since that day, all our systems are running and working without errors, however, if you find any errors, please inform us. Also we inform you t…

Showing the 3 most recent of 3 posts we hold for @Bitcontract_cc_official. 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.

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

“BitContract.cc Official” (@Bitcontract_cc_official), 33 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/Bitcontract_cc_official.

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.