﻿<?xml version="1.0" encoding="utf-8"?>
<!--<!DOCTYPE nitf SYSTEM "nitf-3-4.dtd">-->
<nitf>
  <head>
    <title id="Title">#Title</title>
    <docdata management-doc-idref="">
      <date.issue id="CreationDate" norm="" />
      <du-key id="rev-ver" generation="1" version="Default" />
      <du-key id="Parent-Version" version="" />
      <identified-content>
        <classifier id="newspro-nitf" value="r2" />
        <classifier id="Newspro-App" value="Epaper" />
        <classifier id="Content-Type" value="Story" />
        <classifier id="storyID" value="" />
        <classifier id="CmsConID" value="" />
        <classifier id="Desk" value="" />
        <classifier id="Source" value="" />
        <classifier id="Edition" value="" />
        <classifier id="Category" value="-1" />
        <classifier id="UserName" value="" />
        <classifier id="PublicationDate" value="21/08/2026" />
        <classifier id="PublicationName" value="HI" />
        <classifier id="IsPublished" value="Y" />
        <classifier id="IsPlaced" value="Y" />
        <classifier id="IsCompleated" value="N" />
        <classifier id="IsProofed" value="N" />
        <classifier id="User" value="" />
        <classifier id="Headline-Count" value="" />
        <classifier id="Slug-Count" value="0" />
        <classifier id="Photo-Count" value="0" />
        <classifier id="Caption-Count" value="0" />
        <classifier id="Word-Count" value="0" />
        <classifier id="Character-Count" value="0" />
        <classifier id="Location" value="" />
        <classifier id="TemplateType" value="1" />
        <classifier id="StoryType" value="Story" />
        <classifier id="Author" value="" />
        <classifier id="UOM" value="mm" />
        <classifier id="NumCol" value="0" />
        <classifier id="kicker" value="" />
        <classifier id="ByLine" value="" />
        <classifier id="DateLine" value="" />
        <classifier id="box-geometry" value="153,1001,488,1332" />
        <classifier id="Layer" value="Default" />
        <classifier id="numcol" value="3" />
        <classifier id="ArticleStyle" value="" />
        <classifier id="Epaper-Build" value="7.96.0.0" />
        <classifier id="ProcessingDateTime" value="Thu Aug 20 2026 23:47:15 GMT+0530" />
      </identified-content>
      <urgency id="home-page" ed-urg="0" />
      <urgency id="priority" ed-urg="0" />
      <doc-scope id="scope" value="0" />
    </docdata>
    <pubdata type="print" name="HI" date.publication="20260821T000000+5.30" edition.name="WGL" edition.area="WGL" position.section="21MAIN05FWGL" position.sequence="5" ex-ref="21MAIN05FWGL.indd" />
  </head>
  <body boxBorderWeightColor="" boxBorderWeight="">
    <body.head>
      <hedline>
        <hl1 id="Headline1" class="1" style="Headline1">
          <lang class="3" style="Headline1" font="Franklin Gothic Book" fontStyle="Regular" size="40">Centre limits SIM cards to 9 per person</lang>
        </hl1>
      </hedline>
    </body.head>
    <body.content id="Bodytext" CaptionAsBody="0">
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Italic" size="9">Continued from P1</lang>
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9"></lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">The DoT has also put in place a mechanism to help telecom operators identify such subscribers. From August 23, a representative image of the photo of each subscriber who has already reached the prescribed limit for mobile connections in their name will be made available on the DIP.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">The DIP uses subscriber information submitted by telecom operators. The latest directive requires operators to use the platform to help identify people who have already reached the permitted limit.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">The DoT has asked telecom operators to streamline the process with the Digital Intelligence Platform before November 30. "Till the time such measures are implemented by a TSP on a post-facto basis, as per terms and conditions of the Customer Application Form (CAF), any mobile connection activated beyond the prescribed limit for a day shall be immediately suspended till resolution of the issue in respect of crossing the permitted limit for mobile connections," the circular said.</lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">The government said the objective is to ensure that each subscriber is able to subscribe to and use mobile connections only within the prescribed limit. Under existing instructions issued on August 9, 2012, an individual customer can have a maximum of nine mobile connections in their name across all telecom service providers and all licensed service areas in the country. However, the limit is lower in certain regions. Subscribers in Jammu and Kashmir, Assam and the North-East can have a maximum of six mobile connections. The latest development is about enforcement of the existing limit. The instructions also require customers to provide a declaration in the Customer Application Form (CAF) regarding the mobile connections already held in their name across telecom operators and licensed service areas. The DoT said the respective Licensed Service Areas (LSAs) will be the competent authorities to decide issues arising from the implementation of the instructions.</lang>
      </p>
    </body.content>
  </body>
</nitf>