Access Official Technical PDF

Share Summary:LinkedInEmail

Pledged shares data is a record of listed securities and the quantities identified as being under pledge at a specified date. The disclosure dated June 30, 2020, presents this information as a long, line-by-line inventory: each entry pairs an ISIN with a security description and a quantity. For technical and business teams that work with structured records, the list offers a useful example of why identifiers, units, dates and source limitations matter when reviewing tabular data.

This is a historical snapshot, not a live position report. Its figures describe the listed securities and quantities shown in the document as of June 30, 2020. The entries alone do not establish why shares were pledged, who pledged them, their market value or what happened after that date.

How the pledged shares data is organized

The table has three principal fields: ISIN, ISIN Name and Quantity Under Pledge. The ISIN is the identifier assigned to a security in the listing. The name field supplies a human-readable description, while the quantity field gives the number of shares reported under pledge for that entry.

These fields serve different purposes. A company name helps a reader recognize an issuer, but the ISIN is the more precise reference for distinguishing a particular listed security. The quantity gives a count of shares; it is not a monetary amount. Keeping these meanings separate is essential when copying the disclosure into a spreadsheet, database or reporting workflow.

What security descriptions tell you

Security names in the list include details such as equity share type and, in many cases, face value or a note about a subdivision, split, capital reduction or other corporate action. For example, some descriptions specify shares after a split or subdivision, while others identify differential voting rights. These details are part of the recorded security description and should not be silently discarded during data handling.

Such wording can make the list difficult to scan, especially when company names and descriptions vary in length or formatting. A reliable review should preserve the original text alongside any cleaned or standardized version. That approach makes it possible to search consistently without losing context that may be relevant to identifying the particular security.

Why the date and units matter

The disclosure’s “as on June 30, 2020” date defines its time boundary. It should not be treated as evidence of current pledged holdings. Anyone using the information in a later analysis should retain the reporting date and make clear that it is historical. The document does not provide a time series, so it cannot show whether a quantity increased, decreased or remained unchanged.

Likewise, “Quantity Under Pledge” is a share count. It does not provide the total number of shares issued, the proportion of an issuer’s shares pledged, a valuation, or the terms of any pledge. Those measures would require additional information not contained in the listed fields. Comparing raw quantities across different companies can therefore be misleading: the table provides counts, not a normalized comparison of ownership or financial exposure.

Practical checks when working with the list

When transcribing or processing a disclosure like this, a few basic controls help protect the meaning of the source:

  • Keep the reporting date. Store June 30, 2020, as an explicit attribute rather than leaving it only in a document heading.
  • Preserve the ISIN exactly. Use it as a reference key and avoid relying on company-name matching alone.
  • Retain quantities as numeric counts. Do not interpret them as currency or percentages.
  • Keep the original security description. Notes about share classes, face value and corporate actions may help distinguish entries.
  • Check for transcription errors. Compare extracted records against the document, particularly where line breaks, spacing or unusual identifiers may complicate copying.
  • Record the scope. The supplied material is a portion of a longer document and ends mid-list; it should not be represented as a complete register.

What the disclosure does not establish

A list of pledged quantities is not, by itself, an explanation of the pledge or an assessment of its implications. The table does not state the pledgee, the borrower, the reason for the arrangement, the value of the shares, or the associated contractual conditions. It also does not establish whether a pledge was subsequently released or changed. Those questions require other records and should not be answered by inference from the quantity column.

The distinction is important for analysts and operational decision-makers who may consume financial information through reports or data systems. A well-structured record can make a disclosure easier to search and compare, but processing does not expand what the underlying fields actually say. Clear field definitions and visible provenance help prevent a precise-looking dataset from being used to support unsupported conclusions.

Conclusion

The June 30, 2020, pledged shares data is best read as a dated inventory of listed securities, identified by ISIN, with a reported share quantity for each entry. Its descriptions may include important share-class and corporate-action details, while its quantities remain counts rather than values or percentages. For dependable reuse, preserve the date, identifiers, descriptions and source scope—and treat questions beyond those fields as requiring additional evidence.

Access Official Technical PDF

About The Author