Telegram RegisterThe public register of Telegram
Telegram profile photo for App Box Sign | Сертификат разработчика | Scarlet | ESign

Bot

App Box Sign | Сертификат разработчика | Scarlet | ESign

@appboxsignbot

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

51,474monthly users

+6,190 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID6262476650
TypeBot
Username@appboxsignbot
First recorded12 August 2026
Last confirmed live12 November 2026
Measurements held48
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/appboxsignbot

Topic

Software piracy — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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

44,63952,62848,633.56 August 2026 — 45,284 monthly users7 August 2026 — 47,189 monthly users9 August 2026 — 47,675 monthly users11 August 2026 — 47,103 monthly users12 August 2026 — 47,103 monthly users12 August 2026 — 49,165 monthly users16 August 2026 — 48,414 monthly users18 August 2026 — 48,456 monthly users19 August 2026 — 48,583 monthly users22 August 2026 — 47,332 monthly users24 August 2026 — 48,178 monthly users25 August 2026 — 48,060 monthly users26 August 2026 — 48,441 monthly users27 August 2026 — 48,703 monthly users28 August 2026 — 48,686 monthly users30 August 2026 — 48,706 monthly users31 August 2026 — 48,633 monthly users2 September 2026 — 48,180 monthly users5 September 2026 — 47,338 monthly users8 September 2026 — 47,077 monthly users11 September 2026 — 46,404 monthly users13 September 2026 — 46,144 monthly users15 September 2026 — 44,639 monthly users19 September 2026 — 46,174 monthly users26 September 2026 — 49,669 monthly users4 October 2026 — 49,585 monthly users9 October 2026 — 50,263 monthly users13 October 2026 — 50,577 monthly users15 October 2026 — 50,779 monthly users17 October 2026 — 50,559 monthly users18 October 2026 — 49,220 monthly users19 October 2026 — 51,044 monthly users22 October 2026 — 50,105 monthly users24 October 2026 — 50,089 monthly users24 October 2026 — 50,848 monthly users26 October 2026 — 49,772 monthly users27 October 2026 — 51,561 monthly users28 October 2026 — 51,670 monthly users29 October 2026 — 51,516 monthly users31 October 2026 — 49,869 monthly users2 November 2026 — 51,566 monthly users3 November 2026 — 51,691 monthly users4 November 2026 — 51,795 monthly users6 November 2026 — 50,249 monthly users7 November 2026 — 51,758 monthly users8 November 2026 — 52,100 monthly users10 November 2026 — 52,628 monthly users12 November 2026 — 51,474 monthly users51,4746 August 202612 November 2026
48 measurements spanning 98 days, net +6,190. 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 43,441–53,826 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 48
Measured (UTC)Monthly usersChange
12 Nov 2026, 17:1051,474-1,154
10 Nov 2026, 10:4952,628+528
8 Nov 2026, 22:1652,100+342
7 Nov 2026, 16:5551,758+1,509
6 Nov 2026, 15:1450,249-1,546
4 Nov 2026, 16:0951,795+104
3 Nov 2026, 12:4751,691+125
2 Nov 2026, 15:2751,566+1,697
31 Oct 2026, 18:5049,869-1,647
29 Oct 2026, 20:5651,516-154
28 Oct 2026, 17:4051,670+109
27 Oct 2026, 20:2951,561+1,789
26 Oct 2026, 22:1549,772-1,076
24 Oct 2026, 20:5650,848+759
24 Oct 2026, 00:3150,089-16
22 Oct 2026, 03:4050,105-939
19 Oct 2026, 20:5151,044+1,824
18 Oct 2026, 19:0949,220-1,339
17 Oct 2026, 18:1150,559-220
15 Oct 2026, 21:4050,779first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Mentions

Named by 17 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.

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

“App Box Sign | Сертификат разработчика | Scarlet | ESign” (@appboxsignbot), 51,474 monthly users as measured 12 November 2026. Telegram Register, tgregister.com/channel/appboxsignbot.

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.