Telegram RegisterThe public register of Telegram

Channel

Automationforum.co - Instrumentation and automation

@Automationforum

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

11,619subscribers

+14 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001498716157
TypeChannel
Username@Automationforum
DescriptionInstrumentation, industrial automation, home automation
CreatedBetween 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live12 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/Automationforum

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 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 why it has no browse page of its own yet.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@F0rumElectrical/29736 Aug 2026, 16:36 UTC@Automationforum/17375 · this entry6 Aug 2026, 16:44 UTC1.008 minutes
@Automationforum/17374 · this entry6 Aug 2026, 16:36 UTC@F0rumElectrical/29746 Aug 2026, 16:37 UTC1.00under a minute
@F0rumElectrical/29757 Aug 2026, 11:51 UTC@Automationforum/17385 · this entry7 Aug 2026, 11:57 UTC1.005 minutes
@F0rumElectrical/29767 Aug 2026, 12:00 UTC@Automationforum/17386 · this entry7 Aug 2026, 12:04 UTC1.004 minutes
@F0rumElectrical/29777 Aug 2026, 14:42 UTC@Automationforum/17388 · this entry7 Aug 2026, 14:50 UTC1.008 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@F0rumElectrical5 (5/5 hand-verifiable sample passed)1.005 minutes@F0rumElectrical (41)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 4 of the 4 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 6 August 2026 to 8 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @F0rumElectrical. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

11,60511,62011,612.58 August 2026 — 11,605 subscribers8 August 2026 — 11,605 subscribers9 August 2026 — 11,611 subscribers10 August 2026 — 11,612 subscribers11 August 2026 — 11,620 subscribers12 August 2026 — 11,619 subscribers11,6198 August 202612 August 2026
6 measurements spanning 4 days, net +14. 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 11,603–11,622 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 12:4611,619-1
11 Aug 2026, 09:4411,620+8
10 Aug 2026, 08:1111,612+1
9 Aug 2026, 05:0311,611+6
8 Aug 2026, 02:3211,605no change
8 Aug 2026, 01:0411,605first reading

Engagement

74 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 12 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.991%
avg views ÷ 11,619 subscribers
Avg views / post
115
74 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
74
of 74 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held74 (6 August 202612 August 2026)
Views total8,518
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 13:03 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
1,330
Videos
52
Links
16,700

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

12 Aug 2026, 11:34 UTC46 viewsread 12 August 2026

Control Valve Challenge: Fail Open or Fail Close? A cooling water control valve is installed on a critical reactor system. During normal operation: The valve is controlled by the DCS and regulates cooling water flow correctly. Now consider this failure scenario: The instrument air supply suddenly fails. For this process, loss of cooling can cause the reactor temperature to rise rapidly. What should the control valve

12 Aug 2026, 11:34 UTC33 viewsread 12 August 2026

Top Industrial Cyber Security Companies 📌 Read Full Guide: https://automationforum.co/top-industrial-cyber-security-companies/ Topic: Top industrial cyber security companies and solutions. In this article, you’ll get: ✅ Industrial cybersecurity landscape overview. ✅ Companies and technologies supporting OT security. ✅ Importance of protecting industrial control systems. 🎯 Especially useful for: 👷 Automation and contr

12 Aug 2026, 09:31 UTC75 viewsread 12 August 2026

PROFIBUS PA Physical Layer 📌 Read Full Guide: https://forumautomation.com/t/what-is-the-physical-layer-of-profibus-pa/14288/2 Topic: What is the physical layer of PROFIBUS PA. In this article, you’ll get: ✅ PROFIBUS PA physical layer fundamentals. ✅ Understanding fieldbus communication and signal transmission. ✅ Practical knowledge of PA instrumentation networks. 🎯 Especially useful for: 👷 Instrumentation engineers 🏭

12 Aug 2026, 06:43 UTC112 viewsread 12 August 2026

Control Valve Stroke Length Calculator 📌 Read Full Guide: https://automationforum.co/control-valve-stroke-length-calculator/ Topic: Control valve stroke length calculator. In this article, you’ll get: ✅ Control valve stroke length calculation. ✅ Understanding valve travel and actuator movement. ✅ Practical support for valve sizing and engineering calculations. 🎯 Especially useful for: 👷 Instrumentation engineers 🏭 EP

12 Aug 2026, 03:33 UTC142 viewsread 12 August 2026

SIL Verification Report 📌 Read Full Guide: https://automationforum.co/sil-verification-report-safety-integrity-level-verification-report/ Topic: SIL verification report and safety integrity level verification. In this article, you’ll get: ✅ SIL verification report fundamentals. ✅ Understanding SIF performance and SIL requirements. ✅ Practical insight into safety lifecycle documentation. 🎯 Especially useful for: 👷 Ins

12 Aug 2026, 00:32 UTC132 viewsread 12 August 2026

Cause and Effect Diagrams in Process Industries Quiz 📌 Read Full Guide: https://automationforum.co/cause-and-effect-diagrams-in-process-industries-test-your-knowledge/ Topic: Cause and effect diagrams in process industries quiz. In this article, you’ll get: ✅ Fundamentals of cause and effect diagrams. ✅ Understanding process trips, alarms, and protective actions. ✅ Quiz based learning for process safety and control.

11 Aug 2026, 21:45 UTC117 viewsread 12 August 2026

Essential Control Valve Performance Parameters 📌 Read Full Guide: https://automationforum.co/essential-control-valve-performance-parameters/ Topic: Essential control valve performance parameters. In this article, you’ll get: ✅ Key parameters used to evaluate control valve performance. ✅ Understanding of valve response, accuracy, and stability. ✅ Practical guidance for control valve selection and operation. 🎯 Especial

11 Aug 2026, 18:14 UTC129 viewsread 12 August 2026

Pressure Transmitter Showing 22 mA Troubleshooting 📌 Read Full Guide: https://automationforum.co/pressure-transmitter-showing-22ma-troubleshooting/ Topic: Pressure transmitter showing 22 mA troubleshooting. In this article, you’ll get: ✅ Reasons a transmitter may output 22 mA. ✅ Practical troubleshooting checks. ✅ Understanding transmitter fault and alarm conditions. 🎯 Especially useful for: 👷 Instrumentation enginee

11 Aug 2026, 17:04 UTC126 viewsread 12 August 2026

VFD Variable Frequency Drive Fault Codes 📌 Read Full Guide: https://forumelectrical.com/vfd-variable-frequency-drive-fault-codes/ Topic: VFD variable frequency drive fault codes and troubleshooting. In this article, you’ll get: ✅ Common VFD fault conditions. ✅ Understanding drive alarms and trips. ✅ Practical troubleshooting direction for motor drives. 🎯 Especially useful for: 👷 Electrical engineers 🏭 Maintenance tea

11 Aug 2026, 16:38 UTC123 viewsread 12 August 2026

Transformer Protection with IDMT Relays (Over Current / Earth Fault / Differential) https://forumelectrical.com/transformer-protection-with-idmt-relays-over-current-earth-fault-differential/ Follow Us On: Website: https://www.forumelectrical.com Facebook: https://www.facebook.com/profile.php?id=100091841583670 LinkedIn: https://www.linkedin.com/showcase/91130242/admin/dashboard/ Twitter: https://x.com/ForumEIectrica

11 Aug 2026, 16:19 UTC91 viewsread 12 August 2026

How to Interpret Technical Data Sheet for Low Voltage (LV) Switchgear? https://forumelectrical.com/how-to-interpret-technical-data-sheet-for-low-voltage-lv-switchgear/ Follow Us On: Website: https://www.forumelectrical.com Facebook: https://www.facebook.com/profile.php?id=100091841583670 LinkedIn: https://www.linkedin.com/showcase/91130242/admin/dashboard/ Twitter: https://x.com/ForumEIectrical Pinterest: https://r

Showing the 12 most recent of 74 posts we hold for @Automationforum. 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.

Citation-graph rank

Citation-graph rank — 38,219 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“Automationforum.co - Instrumentation and automation” (@Automationforum), 11,619 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Automationforum.

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.