Independent Information Portal — Not an Official Government or GMADA Website.Read full disclaimer
Ad — Below Header — Leaderboard 728×90 (publisher ID not set)

GMADA Public Notice

Public notice regarding land acquisition for project Expocity SAS Nagar Village Safipur, Ladiaali, Dharamgarh,Rudka.

PublishedOct 2026
FormatPDF
Size533.92 KB
LanguageEnglish
Open Original Document on gmada.gov.in

What the notice identifies

The notice page identifies land acquisition for Expocity in SAS Nagar and names Safipur, Ladiaali, Dharamgarh and Rudka. The supplied information does not establish which parcels are involved, the statutory basis or the procedural stage. Deadlines and directions to landowners are also unconfirmed.

A project name and village list do not, by themselves, define the land affected. The available information does not show whether this notice concerns a proposed acquisition, a later statutory step or another process connected with the project. Those details require the notice text and any schedules or maps attached to it.

What the related Expocity notices establish

Other notice titles tracked on this site refer to Expocity and some of the same village names in 2026. They show related project references, but titles alone do not establish that the notices cover the same parcels or form successive steps in one acquisition process.

The titles record the following:

  • An August 2026 notice is titled as a land-acquisition notice for Expocity and names Safipur, Ladiaali, Dharamgarh and Rudka. Its title also states Mohali tehsil.
  • A September 2026 notice names Rudka, Dharamgadh, Ladiaali and Safipur, but does not identify Expocity in its title.
  • Two October 2026 notices refer to Expocity SAS Nagar and name Saipur, Ladiaali, Dharamgarh and Rudka. They spell the first village Saipur rather than Safipur.
  • A separate August 2026 notice names Niman in connection with establishing Expocity SAS Nagar. Its title does not identify Niman as one of the villages named on this page.

This record shows recurring project references and village names, not a verified acquisition timeline. In particular, the September title does not name Expocity, while the October titles do. Without the documents’ contents, it is not possible to say whether these are separate notices, amendments, notices for distinct parcels or successive steps in one process.

The spelling differences should remain visible when comparing records. The source titles use Safipur on this page and in the August notice, Saipur in the October titles, and both Dharamgarh and Dharamgadh across titles. The available information does not resolve whether these spellings refer to the same places or different ones. Niman appears in a separate Expocity-related August title, but that title alone does not show that it forms part of this page’s village coverage or explain its relationship to the project area.

Ad — Mid-Article — In-Article Native (publisher ID not set)

What is known about the named villages

The page places the subject within the Expocity SAS Nagar project. A related August notice title explicitly refers to Mohali tehsil, but the supplied information does not establish the tehsil or district for each named village individually. It also does not locate the villages relative to particular sectors, roads, landmarks or one another.

“SAS Nagar” in a project title is not a village-by-village location description. The Mohali tehsil wording in another notice title cannot safely be applied to every village named here. The supplied records provide no mapped boundary or verified geographic relationship between Safipur, Ladiaali, Dharamgarh and Rudka.

A shared project reference does not identify the revenue estate, parcel number or boundary covered. The available titles also do not establish whether Safipur and Saipur are the same place, so the spelling difference is not enough to identify land without checking the underlying records. The same caution applies to Dharamgarh and Dharamgadh. Until a notice schedule or other authoritative land record is checked, proximity between the named villages or inclusion of any particular plot cannot be inferred.

What the project references do and do not show

Several tracked notice titles identify Expocity as a project in SAS Nagar and refer to land acquisition or establishment. The recurring village names associate these places with the project in the notices, but the supplied material does not explain why each was included or define the project’s footprint.

The records establish a connection in notice titles, not the planning rationale behind the village list. They do not show whether the villages are part of one contiguous area, whether different notices cover separate project components, or how Niman relates to the other named places. The supplied information identifies no specific sector, infrastructure feature or land-use provision that would explain the project’s intended layout.

The available information does not establish whether the current notice is a proposal, a statutory acquisition notice, a response to an earlier step or a final decision. It provides no verified account of compensation, objections, hearings or implementation. A project reference in a title does not establish that a particular holding is affected or that landowners currently need to take action.

The reliable point is that Expocity appears in multiple 2026 notice titles, with overlapping village names and variations in spelling. That pattern supports comparing the actual documents, but it does not establish approval, acquisition completion, a project boundary or a change in the status of any parcel.

Practical Details

  • Notice Date : October 28, 2026

For more information and complete details, click on “Open Original Document” to view the official source.


Ad — End of Article — In-Article Native (publisher ID not set)
Where this comes from: This is a summary of a notice published by GMADA. The original document lives on GMADA's own website — gmada.gov.in — use the download button above to view or save it.
Ad — Above Footer — Leaderboard 728×90 (publisher ID not set)