Navigate by cohort
Open an ISO week and publication date, then retain every Main and Supplementary Gazette as its own traceable source.
Week 25 · Main + Supplementary
Lex Gazette South Africa · authenticated Gazette intelligence
Legal notices, linked to their source and ready for professional scrutiny.
Browse weekly Gazette cohorts, move from a structured notice to the precise source passage, and see legal-entity or person authentication outcomes without losing the published record.
Source fidelityThe public page discloses cohort-level counts only. Named parties, full identifiers and the verbatim Gazette material are shown after professional access.
27ISO week
Main Gazette 549312,229 structured rows
Explicit authenticationVerified, fixed, review and failed outcomes remain visible.
Source-to-row linkageMove between the published text and its normalized record.
Weekly cohortsMain and Supplementary Gazettes stay distinct under one date.
Matter-ready exportsFilter, copy and export structured notice data for review.
Latest cohort intelligence
Week 27 · 3 July 2026
Government Gazette 54931 · Main Gazette · 208 pages · 19 formal sections.
Cohort sourceDROP244production HTML scan
2,229Structured notices
1,921Distinct estate references
2,524Distinct published IDs / RegNos
2,595Distinct resolved IDs / RegNos
Entity authentication
2,785 classified outcomes98.3%successful
Directly authenticated2,612
Authenticated by default3
Fixed and authenticated124
Unauthenticated / broken41
Rejected fixes / review5
An outcome is counted for each named entity authentication block; a notice can therefore contribute more than one outcome where spouses, applicants, purchasers or counterparties are present.
Estate-reference authentication
2,109 reference occurrences99.0%of classified checks resolved
Authenticated directly1,600
Broken, fixed and resolved71
Unauthenticated17
No estate-URN outcome421
The “no estate-URN outcome” group consists principally of insolvency and appointment forms that carry an estate or reference number but do not expose the same estate-registry outcome used in J193/J187.
Per-form cohort profile
Counts are computed from the real Gazette 54931 production tables. Identifier counts are populated fields, not necessarily one per notice.
| Form / section | Notices | Published IDs / RegNos | Resolved IDs / RegNos | Estate refs | Authenticated | Fixed + auth. | Unauth. / broken | Review |
|---|---|---|---|---|---|---|---|---|
| 11 | 10 | 20 | 0 | 9 | 10 | 2 | 0 | |
| 6 | 6 | 6 | 0 | 6 | 0 | 0 | 0 | |
| 8 | 7 | 8 | 0 | 7 | 0 | 1 | 0 | |
| 40 | 27 | 28 | 0 | 15 | 22 | 5 | 0 | |
| 1 | 0 | 1 | 1 | 0 | 1 | 0 | 0 | |
| 28 | 19 | 41 | 0 | 19 | 13 | 17 | 0 | |
| 11 | 0 | 0 | 11 | 0 | 0 | 0 | 0 | |
| 909 | 1,189 | 1,199 | 909 | 1,163 | 20 | 4 | 2 | |
| 779 | 999 | 1,003 | 779 | 980 | 14 | 4 | 1 | |
| 17 | 17 | 16 | 17 | 14 | 2 | 1 | 0 | |
| 27 | 28 | 28 | 27 | 26 | 2 | 0 | 0 | |
| 13 | 13 | 13 | 13 | 12 | 0 | 0 | 1 | |
| 100 | 101 | 105 | 100 | 97 | 6 | 1 | 0 | |
| 33 | 29 | 36 | 33 | 29 | 6 | 0 | 0 | |
| 84 | 88 | 93 | 84 | 81 | 8 | 3 | 0 | |
| 66 | 65 | 70 | 66 | 63 | 7 | 0 | 0 | |
| 13 | 18 | 18 | 13 | 18 | 0 | 0 | 0 | |
| 56 | 45 | 58 | 56 | 41 | 13 | 3 | 1 | |
| 27 | 32 | 32 | 0 | 32 | 0 | 0 | 0 |
Designed around the way legal professionals investigate notices.
The service carries forward the working features of the source packs: date-first navigation, Gazette-level designation, section maps, source text, structured tables, row-level source markers, authentication states and export tools.
Search structured notices
Filter across form, province, party, matter type and authentication outcome without scanning hundreds of Gazette pages.
J193 · Gauteng · Review requiredPreserve source context
Keep the source extract available beside the normalized record and expose Gazette number, date, page and section provenance.
Gazette 54931 · p. 15 · BSNOTInspect authentication
See cleaned names, masked identifiers, legal-entity class, confidence and any correction or mismatch that requires professional review.
Fixed & authenticated · 99%Use section maps
Jump directly to Business, Company, Court, Estate, Insolvency and Companies Act forms with page and record counts.
J193 · pages 67–119 · 909 rowsExport a defensible subset
Copy citations or export the filtered register while retaining publication and source-marker fields for downstream work.
CSV · citation · print view
Authentication made inspectable
An authenticated record, not merely a search result.
A search result can tell a practitioner that a name or number appears somewhere in a Gazette. An authenticated record goes further: it preserves what was published, shows the normalized candidate, records the corroborating path, explains any repair, and leaves unresolved conflicts visible for professional review.
Demonstration data only. Every name, date, address, Gazette reference, estate reference and identifier in the examples below is fictional, composite, masked or deliberately altered. No example represents a real person, company or estate.
Search result
“This text appears to match.”
A conventional search can retrieve the passage, but it does not necessarily explain which field was rendered incorrectly, whether the identifier belongs to the named party, or why a candidate should be trusted.
Matching textKeyword proximityNo repair historyNo reasoned outcome
Authenticated record
“This is what was published, what was resolved, and why.”
The professional view keeps the source marker, rendered values, cleaned values, entity class, evidence narrative, confidence band and exception state together. The published record is never silently overwritten.
Source provenanceRendered + clean valuesReasoned evidenceExplicit review state
01Capture the publicationRetain the Gazette, date, page, form and verbatim rendered field.
02Normalize without erasingSeparate names, references and identifiers while preserving the original.
03Classify the partyDistinguish a person, company, estate reference or other legal entity.
04Corroborate or repairTest the rendered value and any transparent correction against supporting evidence.
05Publish the outcomeShow the match, confidence, repair path, failure or review requirement.
Example 01 · source linkage
Synthetic business notice
From the Gazette passage to an explainable identity outcome.
The source remains readable beside the structured record. A practitioner can see the spelling and registration number as rendered, the clean candidate, and the precise reason that a repair was accepted.
Published source passageMocked and masked
BUSINESS NOTICES · DEMONSTRATION PROVINCE
Notice is hereby given in terms of the applicable statutory publication requirements...
◆ CAPE MERIDIAN; (2) SILVER ACACIA HOSPITALTY (PTY) LTD; registration 0215/••••••/07; (3) a hospitality enterprise at 18 Example Avenue; (4) transfer as a going concern; (5) BLUE CRANE TRADING (PTY) LTD; (7) Sample & Example Attorneys.
The rendered passage is retained exactly for professional comparison.
Normalized and authenticated recordSource marker 01
Rendered nameSilver Acacia Hospitalty (Pty) Ltd
Clean nameSilver Acacia Hospitality (Pty) Ltd
Rendered registration0215/••••••/07
Clean registration2015/••••••/07
Form and sourceBSNOT · Demonstration Gazette 55••• · p. 101
Entity class20 Business · private company
Evidence narrativeThe cleaned company name and corrected year prefix corroborate one another. The registration as published does not authenticate and remains visible as the rendered value.
PublishedWhat the Gazette actually rendered
The misspelling and malformed year prefix remain available for evidential comparison.
ResolvedWhat the clean candidate says
The normalized name and registration are shown separately rather than replacing the source.
ReasonWhy the outcome was accepted
The evidence narrative records the corroboration and the exact fields that required repair.
Example 02 · business entities
Composite company examples
Different repair paths receive different, visible outcomes.
The table presentation mirrors the professional reader: rendered and clean values sit side by side, while the legal-entity cell and evidence narrative show whether a single repair, a multi-field resolution or no defensible match occurred.
| Rendered Name | Idn/RegNo | Clean Name | Clean Idn/RegNo | Legal Entity | Authentication Status |
|---|---|---|---|---|---|
| Silver Acacia Hospitalty | 0215/••••••/07 | Silver Acacia Hospitality (Pty) Ltd | 2015/••••••/07 | ✓ 20 BusinessFixed and authenticated | 99%+ illustrative confidenceCleaned name corroborates the corrected registration.Published registration fails authentication and is retained as rendered. |
| Blue Crane Mining Servlces | 2016/5I3••O/07 | Blue Crane Mining Services (Pty) Ltd | 2016/513••0/07 | ✦ 20 BusinessMulti-field repair and resolution | 99%+ illustrative confidenceOCR substitutions in both the name and registration were repaired.The combined clean fields corroborate one entity; the rendered pair does not. |
| Kopano Advisory Group | 2019/••••••/07 | Kopano Advisory Group (Pty) Ltd | — | ! Review requiredNo forced match | Candidate name onlyThe name is plausible, but the published registration does not corroborate it.No clean identifier is substituted; the record remains unresolved. |
Why this matters: a successful repair is not merely a cleaner string. The record must show which value failed, which candidate was accepted and what evidence justified that decision.All names and identifiers are synthetic and masked.
Example 03 · estates and persons
Composite estate examples
Estate references, names and personal identifiers are assessed independently.
A single notice may contain a valid estate reference, a damaged estate number, a name variant and an identifier error. The reader exposes each element separately so that a professional can distinguish a direct match, an authoritative-reference resolution, a repaired field and an unresolved conflict.
| Estate Number | Name | Date of birth | Id-number | Clean Name | Clean Id-number | Legal Entity | Authentication Status |
|---|---|---|---|---|---|---|---|
| 0119••/20269922026EST01•••• | Naledi M. Dlamini | 1953-07-20 | 53••••5370088 | Naledi Mpho Dlamini | 53••••5730088 | ✓ 10 ResidentialFixed and authenticated | 94–99% illustrative confidenceRendered name corroborates the clean name.Published identifier fails; corrected candidate aligns with the estate record. |
| 0115••/20269922026EST01•••• | Mariette van Tonder | 1938-01-30 | 38••••5055080 | Mariette van Tonder | 38••••0041082 | ✦ 10 ResidentialAuthoritative-reference resolution | 99%+ illustrative confidenceThe estate reference corroborates the clean identity after an identifier repair.The reason for accepting the repaired value is recorded. |
| ⚠ ✦ Broken 01?3••/20269922026EST01•••• |
Anton C. Winter | 1943-01-30 | 43••••5039088 | Anton Coenraad Winter | 43••••5069088 | ✓ 10 ResidentialFixed and authenticated | 94–99% illustrative confidenceThe estate number is visibly marked as broken; a derived reference is retained separately.Name and repaired identifier corroborate without hiding the source defect. |
| 0303••/20259922025EST03•••• | Thabo Molefe | 1967-01-04 | 67••••5994081 | Thabo Molefe | 67••••5994081 | 10 ResidentialDirectly authenticated | 90–99% illustrative confidenceRendered name and masked identifier corroborate directly.No repair is applied. |
| 0276••/20259922025EST02•••• | Lerato N. Mokoena | 1981-06-15 | 81••••0636089 | Lerato Nandi Mokoena | — | ! Review requiredIdentifier conflict | No authenticated identifierThe name variant is plausible, but the rendered identifier resolves inconsistently.The system refuses to insert a replacement without sufficient corroboration. |
Exception-first presentation: damaged estate numbers, name repairs and identifier conflicts remain conspicuous. A professional reviewer can see the published defect before considering the clean candidate.Fictional composite examples · not legal advice.
Fixed and authenticatedA transparent, evidence-supported correction produced a corroborated identity.
Resolved through a stronger pathMultiple fields or an authoritative reference were required to support the outcome.
Broken published fieldThe defect remains visible even where another field can be resolved.
Review requiredNo candidate is silently promoted where the evidence remains inconsistent or incomplete.
Authentication is an inspectable research outcome, not an identity warranty. The official Gazette remains the authoritative publication. Lex Gazette preserves the source, makes its normalization and evidence path visible, and gives the professional user the information required to verify or challenge the outcome.
A transparent method
Corrections are surfaced, not silently substituted.
The strongest proposition for legal users is the combination of source fidelity and explicit authentication. Every normalized record should retain its Gazette provenance, show what was rendered, show the cleaned or matched identity, and visibly flag any uncertainty.
22Weekly cohorts
30Gazettes
130Sections
7,018Structured rows
01
Retain the publication unit
Each Main or Supplementary Gazette remains independently identifiable inside its weekly cohort.
02
Normalize the formal notice
Published fields are separated into a consistent register suitable for searching, filtering and export.
03
Link back to the source marker
A structured row can return the professional reviewer to the relevant source passage and Gazette page.
04
Expose authentication and exceptions
Successful matches, fixed identifiers, likely matches and failures receive visibly different legal-review states.