بابل /الاسكندرية
Signed *

Channel
@wazfnyi
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
17,169subscribers
+1,660 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001473512936 |
|---|---|
| Type | Channel |
| Username | @wazfnyi |
| Description | قناة لتوفير وظائف شاغرة في بابل مجانااااا ادمن Ph_Marss رجاءا عدم مراسلتي الا في حين وجود وظيفه شاغره للنشر.. يمنع مراسله الادمن لطلب وظيفة 🚫 ⚠️لا نتعامل مع شركات التوظيف |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/wazfnyi |
Job listings — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
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.
Posts published here appear in near-verbatim form on 6 other registered channels. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @wazfnyi/34136 · this entry8 Aug 2026, 19:54 UTC | @kotaybaeng96/492219 Aug 2026, 11:10 UTC | 1.00 | 15 hours |
| @wazfnyi/34455 · this entry19 Aug 2026, 17:18 UTC | @kotaybaeng96/4938520 Aug 2026, 19:41 UTC | 1.00 | 26 hours |
| @wazfnyi/34646 · this entry26 Aug 2026, 20:15 UTC | @kotaybaeng96/4945027 Aug 2026, 08:45 UTC | 1.00 | 13 hours |
| @wazfnyi/34655 · this entry27 Aug 2026, 07:39 UTC | @kotaybaeng96/4945127 Aug 2026, 08:45 UTC | 1.00 | 65 minutes |
| @wazfnyi/34781 · this entry1 Sept 2026, 16:36 UTC | @kotaybaeng96/495462 Sept 2026, 07:14 UTC | 1.00 | 15 hours |
| @wazfnyi/34784 · this entry1 Sept 2026, 17:03 UTC | @kotaybaeng96/495492 Sept 2026, 07:14 UTC | 1.00 | 14 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @kotaybaeng96 | 8 (8/8 hand-verifiable sample passed) | 1.00 | 13 hours | this entry (8–0) |
| @jobs_iraq1 | 6 (6/6 hand-verifiable sample passed) | 1.00 | 3.6 hours | this entry (5–1) |
| @Jopaalanat | 5 (5/5 hand-verifiable sample passed) | 1.00 | 16 hours | @Jopaalanat (5–0) |
| @eng7600 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 5.2 hours | this entry (3–2) |
| @plm3132 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 30 hours | this entry (5–0) |
| @YSPjobs | 5 (5/5 hand-verifiable sample passed) | 1.00 | 1.7 hours | @YSPjobs (3–2) |
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. 11 of the 11 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 267 comparable posts for this entry, running 7 August 2026 to 14 November 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.
Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 15 November 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 17:47 | 17,169 | +52 |
| 10 Nov 2026, 00:16 | 17,117 | +8 |
| 8 Nov 2026, 13:39 | 17,109 | +7 |
| 7 Nov 2026, 08:41 | 17,102 | +10 |
| 6 Nov 2026, 05:57 | 17,092 | +10 |
| 5 Nov 2026, 03:28 | 17,082 | +3 |
| 4 Nov 2026, 02:19 | 17,079 | +2 |
| 3 Nov 2026, 02:29 | 17,077 | +12 |
| 2 Nov 2026, 01:19 | 17,065 | +17 |
| 31 Oct 2026, 23:16 | 17,048 | +4 |
| 31 Oct 2026, 01:37 | 17,044 | +7 |
| 29 Oct 2026, 23:28 | 17,037 | -1 |
| 29 Oct 2026, 01:30 | 17,038 | -4 |
| 28 Oct 2026, 01:40 | 17,042 | +12 |
| 27 Oct 2026, 02:25 | 17,030 | +12 |
| 25 Oct 2026, 23:19 | 17,018 | +11 |
| 24 Oct 2026, 22:46 | 17,007 | +5 |
| 23 Oct 2026, 20:07 | 17,002 | +14 |
| 22 Oct 2026, 18:10 | 16,988 | +15 |
| 21 Oct 2026, 14:49 | 16,973 | first reading |
676 posts held, back to 7 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 77 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 14 November 2026 |
|---|---|
| Posts held | 676 (7 August 2026 – 14 November 2026) |
| Views total | 328,738 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Nov 2026, 05:41 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.
Lifetime counters from Telegram’s own channel header, read 15 November 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.
Telegram’s own ‘edited’ marker: 9 of 202 posts held from the last 30 days (4.46%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
بابل /الاسكندرية
Signed *
سلام عليكم ست محتاج عمال ٢ من ٥ صباحا ل ٣ ضهرا العمل مطعم غسل صاله 07844209988
📢 فرصة عمل – محافظة بابل تعلن شركة سلامتي الطبية عن حاجتها إلى مندوبة للعمل ضمن فريقها في محافظة بابل. ✨ مميزات العمل: وقت عمل قصير ومرن. طبيعة عمل سهلة وبسيطة. راتب بسيط ومناسب لطبيعة العمل. مطلوب مندوبه لبقة بالكلام ولديها مهارة اقناع اهم نقطه 📍 مكان العمل: محافظة بابل. على من تجد في نفسها الرغبة بالعمل والاستعداد للانضمام، يرجى التواصل للاستفسار عل واتساب 07874094147
بغداد
Signed *
بغداد
Signed *
تحيه طيبه مكتب علمي رصين بحاجه لمندوبة صيدلانية اعلام دوائي لاين جلديه فقط ويشترط الخبره المسبقه بهذا اللاين على من تتوفر لديها الخبره ارسال السيفي على الايميل التالي [email protected] --------------------
Signed *
https://www.facebook.com/share/1GNEJnwJXD/بابل
Signed *
محتاجين عامل بكراج غسل سيارات بالاسكان بابل لمعلومات اكثر اتصل برقم الواتس اب 07843218008 فقط واتس مو مكتب تشغيل احنه كبل تجي تشتغل بدون لا عموله ولا مكتب
Signed *
https://www.instagram.com/k_kayaspa?rpxt=b2o1YmhiMHk5MHFu/بابل
Signed *
بغداد
Signed *
بابل
Signed *
تعلن شركة السبطين للمقاولات العامة المحدودة في كربلاء عن حاجتها : موظفات مبيعات المهام والمسؤوليات • البحث عن عملاء جدد وتوسيع قاعدة العملاء. • التواصل مع العملاء . • فهم احتياجات العميل وتحويلها إلى افكار وفرص بيع حقيقية. • متابعة مؤشرات الأداء وتحقيق أهداف المبيعات الشهرية والسنوية. • تمثيل الشركة بصورة مهنية المؤهلات المطلوبة • شهادة جامعية • خبرة في المبيعات العقارات حصرا • قدرة عالية على الإقناع والتفاوض.…
Showing the 12 most recent of 676 posts we hold for @wazfnyi. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
@wazfnyi named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 20 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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“وظفني♥️بابل ♥️” (@wazfnyi), 17,169 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/wazfnyi.
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.