Channel
@horizonsecurity
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
1,369subscribers
-44 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001407014960 |
|---|---|
| Type | Channel |
| Username | @horizonsecurity |
| Created | Between 1 April 2019 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/horizonsecurity |
Technology — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 16:58 | 1,369 | -1 |
| 13 Sept 2026, 02:18 | 1,370 | -3 |
| 8 Sept 2026, 18:37 | 1,373 | -8 |
| 3 Sept 2026, 14:38 | 1,381 | -5 |
| 31 Aug 2026, 16:47 | 1,386 | -9 |
| 28 Aug 2026, 06:54 | 1,395 | -6 |
| 25 Aug 2026, 03:36 | 1,401 | -4 |
| 18 Aug 2026, 16:22 | 1,405 | -3 |
| 15 Aug 2026, 16:26 | 1,408 | -5 |
| 12 Aug 2026, 02:45 | 1,413 | no change |
| 12 Aug 2026, 02:32 | 1,413 | first reading |
15 posts held, back to 18 July 2024 — 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 15 posts for this entry, the most recent from 2 July 2025. An engagement rate over an empty window would be a number about nothing.
Verification of groups in the Horizon security system. Contracts for verification of new groups and objects, group and object updates have been developed. Each group and object in Horizon has a personal FID registered, which forms a new independent branch of the transaction bush. Special parameters used when working with groups and objects have been added to the system parameters contract. Horizon Operations Moni…
Management of users' connection to the Horizon network is available in the web application of the Public Network Operations Monitor. 1) Quick registration of a new profile via email. 2) Authorization: - through a one-time code, which can be requested by email, - by entering a secret key, - via QR scanning from the mobile app. Registration/authorization via third-party applications is also provided. Horizon Operat…
In the operations monitor of the Horizon public network, information about groups and entities that have been verified is available. Verification is performed when creating and modifying an entity in third-party applications. Each entity has its own FID (account), asset transactions are available. Special Entities section - https://ankhorizon.com/groups.
The verification process for all Territory groups and sites that were established prior to the implementation of the group and site verification mechanism in Horizon has been successfully completed. All newly created sites and groups are now subject to automatic verification. https://ankhorizon.com/transactions
The verification of groups and sites within the Horizon security system. In "Territory", groups and sites undergo a verification process both upon their creation and following any updates to their information. This verification is conducted utilizing the tools provided by the autonomous information security system known as "Horizon." From any individual group or site info card, users have the ability to follow a l…
New system contracts for verification of groups and objects used in third-party systems have been registered. Contracts are executed when an authorized request for verification of a new object or group is received. All operations are available in a special section of the Horizon operations monitor https://ankhorizon.com/transactions.
Contract update registration of operation parameters was performed. Added parameters for working with objects and groups used in third-party systems using Horizon. Always up-to-date version of the parameter table - https://ankhorizon.com/params.
In the public network of Horizon the automatic registration of balances of early network users is carried out. To perform balance registration, it is necessary to authorize once in any application. If authorization has not been performed before, the system will first of all verify the user in the network, and then the balance registration will be started. https://ankhorizon.com/transactions
Horizon statistics and analytics server. The tool is built as an independent service with its own computing resources, it is placed outside the main tools of the public network. After the launch of the tool, the load on the public network in case of frequent requests has been significantly reduced. It became possible to analyze data for different periods, build graphs, evaluate the effectiveness of mathematical fo…
After optimizing the logic for block validation confirmation in transactions, the validation speed increased from 2 to 10 times in tests, with each block taking from 0.25 seconds to confirm. To confirm the validation of each block, confirmation services must be requested from 10 other Workers who are not involved in the specific transaction. When confirming the validation of a block, a Worker must perform mathemat…
Updating the Worker page in the Horizon public network operations monitor. https://ankhorizon.com/
In Horizon, it is now possible to download any transaction for offline storage. The received data download includes the entire branch from the root transaction of a united transaction bush to the current transaction. The download is self-sufficient, despite its small size (up to 100kb). Access to the entire public network is not required for integrity checking. You can download a transaction from the page of each …
Showing the 12 most recent of 15 posts we hold for @horizonsecurity. 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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Horizon Security System” (@horizonsecurity), 1,369 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/horizonsecurity.
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.