Channel

KYC Flow

@kycflow

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

1,090subscribers

+319 since we began measuring on 19 September 2026

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

Register entry

Telegram ID	-1003817991402
Type	Channel
Username	@kycflow
Created	Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	9 October 2026
Last confirmed live	2 November 2026
Measurements held	9
Confirmed unchanged	1 time, most recently 2 November 2026
On Telegram	t.me/kycflow

Topic

Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 10 October 2026 and assigned it the closest of 31 fixed categories, at 98% 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

9 measurements spanning 44 days, net +319. 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 723–1,138 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
2 Nov 2026, 07:10	1,090	+21
30 Oct 2026, 16:09	1,069	+14
27 Oct 2026, 23:30	1,055	+27
24 Oct 2026, 18:18	1,028	+54
18 Oct 2026, 09:20	974	+63
11 Oct 2026, 03:19	911	+56
9 Oct 2026, 18:59	855	no change
1 Oct 2026, 17:38	855	+84
19 Sept 2026, 02:48	771	first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 2 November 2026 — this entry's latest reading, not the date you are reading this.

“KYC Flow” (@kycflow), 1,090 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/kycflow.

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.