🔼[2] EURGBP WIN at 0.85401

Channel
Sig-Zy Binary Statistic Official
@SigZySignalOfficial
On this record: Topic · Growth · Engagement · Posts · Cite this entry
5,569subscribers
-361 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001679013102 |
|---|---|
| Type | Channel |
| Username | @SigZySignalOfficial |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/SigZySignalOfficial |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Nov 2026, 21:00 | 5,569 | -16 |
| 10 Nov 2026, 07:58 | 5,585 | -17 |
| 6 Nov 2026, 13:16 | 5,602 | -7 |
| 3 Nov 2026, 06:27 | 5,609 | -4 |
| 31 Oct 2026, 05:27 | 5,613 | -12 |
| 28 Oct 2026, 04:21 | 5,625 | -19 |
| 25 Oct 2026, 04:58 | 5,644 | -13 |
| 22 Oct 2026, 13:38 | 5,657 | -26 |
| 19 Oct 2026, 03:56 | 5,683 | -14 |
| 16 Oct 2026, 01:37 | 5,697 | -17 |
| 13 Oct 2026, 00:18 | 5,714 | -31 |
| 6 Oct 2026, 10:58 | 5,745 | -34 |
| 29 Sept 2026, 17:40 | 5,779 | -19 |
| 19 Sept 2026, 09:18 | 5,798 | -8 |
| 15 Sept 2026, 07:39 | 5,806 | -11 |
| 11 Sept 2026, 13:20 | 5,817 | -16 |
| 6 Sept 2026, 13:57 | 5,833 | -29 |
| 2 Sept 2026, 01:45 | 5,862 | -13 |
| 29 Aug 2026, 21:52 | 5,875 | -1 |
| 26 Aug 2026, 16:58 | 5,876 | first reading |
Engagement
99 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 9 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 99 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
🔼[1] EURGBP WIN at 0.85407
🔼[1] EURGBP WIN at 0.85414
🔽[2] EURJPY WIN at 183.902
🔽[1] EURJPY WIN at 183.884
🔼[1] EURUSD WIN at 1.15353
🔼[1] AUDUSD WIN at 0.70575
🔼[3] EURUSD WIN at 1.15370
🔼[3] GBPUSD WIN at 1.35033
🔼[1] EURUSD WIN at 1.15397
🔽[1] GBPJPY WIN at 215.221
🔽[2] AUDUSD WIN at 0.70656
Showing the 12 most recent of 99 posts we hold for @SigZySignalOfficial. 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 15 November 2026 — this entry's latest reading, not the date you are reading this.
“Sig-Zy Binary Statistic Official” (@SigZySignalOfficial), 5,569 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/SigZySignalOfficial.
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.