Telegram RegisterThe public register of Telegram
Telegram profile photo for Trident Free Logs

Channel

Trident Free Logs

@Trident_Logs

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

2,149subscribers

+156 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003489469660
TypeChannel
Username@Trident_Logs
CreatedBetween 1 November 2025 and 30 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 September 2026
Last confirmed live5 October 2026
Measurements held17
Confirmed unchanged1 time, most recently 5 October 2026
On Telegramt.me/Trident_Logs

Topic

Hacking & security — 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 19 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

1,9932,1492,0717 August 2026 — 1,993 subscribers8 August 2026 — 1,996 subscribers11 August 2026 — 2,003 subscribers14 August 2026 — 2,011 subscribers18 August 2026 — 2,015 subscribers20 August 2026 — 2,032 subscribers24 August 2026 — 2,043 subscribers26 August 2026 — 2,047 subscribers29 August 2026 — 2,063 subscribers2 September 2026 — 2,078 subscribers5 September 2026 — 2,084 subscribers11 September 2026 — 2,091 subscribers14 September 2026 — 2,106 subscribers18 September 2026 — 2,115 subscribers19 September 2026 — 2,115 subscribers28 September 2026 — 2,133 subscribers5 October 2026 — 2,149 subscribers7 August 20265 October 2026
17 measurements spanning 59 days, net +156. 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 1,970–2,172 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Oct 2026, 17:212,149+16
28 Sept 2026, 01:212,133+18
19 Sept 2026, 21:522,115no change
18 Sept 2026, 16:002,115+9
14 Sept 2026, 13:172,106+15
11 Sept 2026, 02:212,091+7
5 Sept 2026, 22:382,084+6
2 Sept 2026, 02:482,078+15
29 Aug 2026, 23:072,063+16
26 Aug 2026, 18:162,047+4
24 Aug 2026, 04:472,043+11
20 Aug 2026, 21:352,032+17
18 Aug 2026, 02:062,015+4
14 Aug 2026, 21:042,011+8
11 Aug 2026, 08:262,003+7
8 Aug 2026, 18:011,996+3
7 Aug 2026, 18:051,993first 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 5 October 2026 — this entry's latest reading, not the date you are reading this.

“Trident Free Logs” (@Trident_Logs), 2,149 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/Trident_Logs.

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.