Skip to main content
Marvipol Development S.A. logo

Marvipol Development S.A. — Investor Relations & Filings

Ticker · MVP ISIN · PLMRVDV00011 LEI · 259400I0C8HBAHH0Y245 WAR Real estate activities
Open in API
Filings indexed 937 across all filing types
Latest filing 2025-03-21 Audit Report / Informat…
Country PL Poland
Listing WAR MVP

About Marvipol Development S.A.

https://www.marvipol.pl/

Marvipol Development S.A. is a real estate development company operating since 1996. The company's activities are concentrated in two primary segments: residential housing and warehouse logistics. In the residential sector, it specializes in the development and sale of multi-family housing projects, including studios, apartments, and family residences. These projects are located in major metropolitan areas such as Warsaw, Wrocław, and the Tri-City (Gdańsk and Gdynia). The company emphasizes high-quality workmanship, modern architecture, and comprehensive land development. In addition to its residential portfolio, Marvipol Development is also active in the development of warehouse and logistics facilities and offers commercial premises for sale.

Recent filings

Filing Released Lang Actions
Wybrane dane finansowe - dokument
Audit Report / Information Classification · 95% confidence The document text provided is heavily truncated and appears to be the raw HTML/CSS structure generated by a PDF conversion tool (indicated by tags like 'html', 'head', 'style', 'font-face', and base64 encoded font data). There is no discernible financial content, regulatory headers (like 10-K, AR, ER), or specific reporting periods within the visible text snippet. The document length is substantial (124,093 chars), suggesting it is a full report, but the content itself is unreadable for classification purposes. Given the lack of content and the nature of the visible text (conversion artifacts), the most appropriate classification is the general fallback category for regulatory filings that cannot be specifically identified, or if this were a real scenario, it would be flagged for manual review. Following the provided rules, since the content is unreadable and does not fit any specific definition, I will use the general fallback category. Q3 2024
2025-03-21 Polish
List Prezesa Zarządu do akcjonariuszy - podpis
Regulatory Filings Classification · 95% confidence The provided document text consists almost entirely of XML structures related to digital signatures (Signature, SignedInfo, KeyInfo, SignatureValue, etc.). This format is characteristic of digitally signed regulatory filings or documents submitted electronically to regulatory bodies, often using XML Digital Signature standards (like XAdES). The content itself does not contain narrative financial results, management discussion, or standard report sections (like 10-K or IR). Since it is a signed document structure that doesn't fit the specific categories like ER, IR, 10-K, or AGM-R, and it represents a formal submission, the most appropriate general classification is the fallback category for miscellaneous regulatory filings that are formally structured and signed, which is Regulatory Filings (RNS). The document length is substantial (10103 chars), but the content type is structural metadata, not the report body itself.
2025-03-21 Polish
List Prezesa Zarządu do akcjonariuszy - dokument
Management Reports Classification · 95% confidence The document text provided is heavily truncated and appears to be the raw HTML/XML structure generated from converting a PDF document, indicated by the presence of extensive CSS styling, font definitions (like @font-face), and HTML tags (head, style, meta). There is no discernible financial report content, regulatory headers (like 10-K, AR, ER), or specific reporting periods mentioned in the visible text snippet. The document length is substantial (84,303 chars), suggesting it is a full report, but the content itself is unreadable/unclassifiable due to truncation and formatting noise. Given the lack of actual content and the presence of formatting artifacts, the most appropriate classification is the fallback category for miscellaneous or unreadable filings, which is Regulatory Filings (RNS), although this is a low-confidence classification based purely on the structure suggesting a complex document that failed to render its content properly in the snippet.
2025-03-21 Polish
Sprawozdanie Niezależnego Biegłego Rewidenta - podpis
Regulatory Filings Classification · 95% confidence The provided document text consists almost entirely of XML structures related to digital signatures (Signature, SignedInfo, KeyInfo, DigestValue, etc.). This structure is characteristic of a digitally signed electronic document, often used for regulatory filings or official corporate communications to ensure authenticity and integrity. Crucially, the document contains references to a file named "Marvipol_JSF_SzB-2024-12-31-0-pl.xhtml" and a signing time of "2025-03-19T17:35:30Z". The presence of a signature block, rather than the content of a financial report itself, suggests this is metadata or a wrapper around the actual content. Since the text does not contain typical financial report sections (like MD&A, Balance Sheet, Income Statement) or explicit announcements of a report's release (like 'We announce the publication of our 10-K'), and given that it is a highly structured, signed document, it most closely aligns with a general regulatory filing or an attachment/wrapper for one. The most appropriate general category for miscellaneous, structured regulatory documents that don't fit specific financial report types (10-K, IR, ER) is 'Regulatory Filings' (RNS). It is not an RPA because it is not a short announcement stating a report is attached; it *is* the signed artifact itself. It is not a specific financial report type (10-K, IR, ER, etc.). Therefore, RNS is the best fit.
2025-03-21 Polish
Sprawozdanie Niezależnego Biegłego Rewidenta - dokument
Audit Report / Information Classification · 95% confidence The document text provided is heavily truncated and consists primarily of HTML structure, CSS styles, and font data generated by a PDF conversion tool ('pdf2htmlEX'). The title tag, "Marvipol_JSF_SzB-2024-12-31-0-pl.xhtml", suggests a financial document related to 'Marvipol' ending on '2024-12-31'. The presence of XBRL tools mentioned in the header suggests a regulatory filing. However, the actual content is missing, and the provided text is just the boilerplate structure of the converted file. Given the length (816,244 chars) and the date ending in '2024-12-31', this is likely a full annual or interim report, but since the content itself is not visible, and we cannot confirm if it is the full 10-K or a shorter IR/ER, we must rely on the context of typical filings associated with year-end dates. If this were a complete, comprehensive report, it would be 10-K (if year-end) or IR (if interim). Since the text is just the container and not the report content, and we cannot definitively identify the specific report type (like 10-K vs IR) from the metadata alone, the safest classification based on the structure being a converted regulatory document, and lacking the actual content to distinguish between 10-K, IR, or AR, is to use the general Regulatory Filings fallback (RNS), or if we assume the date implies a major filing, we might lean towards 10-K or IR. Given the extreme truncation showing only HTML/CSS, and applying the 'MENU VS MEAL' rule (which usually applies to short announcements), this text is not an announcement of a report, but the structure of a converted report. Since we cannot read the content to confirm 10-K (Annual) or IR (Interim), and it is clearly a structured filing, I will default to the most comprehensive annual filing type if the date suggests year-end, which is 10-K, acknowledging the high uncertainty due to missing content. However, the safest classification for an unreadable, structured filing is RNS. Revisiting the definitions: 10-K is the 'Official yearly report'. IR is the 'Comprehensive financial report for a period shorter than a year'. Since the date is 2024-12-31, this strongly suggests a year-end filing, making 10-K the most probable intended type if the document were readable. Since the text is unreadable boilerplate, I will use RNS as the fallback for an unclassifiable structured document, as per Rule 3, unless the structure strongly implies a specific major report type. The presence of XBRL tools points to a formal filing. Given the ambiguity, RNS (Regulatory Filings) is the most appropriate fallback for a document whose content cannot be analyzed but whose structure suggests a formal filing. FY 2024
2025-03-21 Polish
Jednostkowe sprawozdanie finansowe - podpis
Regulatory Filings Classification · 95% confidence The provided document text consists entirely of XML digital signature blocks (specifically XAdES signatures, indicated by namespaces like ds: and xades:). These blocks contain references to a file named "JSF FY 2024_final.xhtml" and signing timestamps (e.g., 2025-03-19T15:57:52Z). The presence of 'FY 2024' suggests a Fiscal Year document, likely a financial report. However, the document itself is not the report content but rather the digital signature metadata attached to it. Since the text is only the signature structure and does not contain the actual financial report content (like an Annual Report (10-K) or Interim Report (IR)), and it is not an announcement *about* a report (RPA), the most appropriate classification for a document consisting solely of regulatory/legal metadata or signature blocks that don't fit other categories is the general fallback category, Regulatory Filings (RNS). The document length is substantial (26k chars), but the content type is purely metadata/signature, not the report itself.
2025-03-21 Polish

Browse filings by year

10 years

Report missing filing

Can't find a specific document? Let us know and we'll add it within 24 hours.

We will notify you once the filing is added.
Report sent
Thank you. We will check the data and update it shortly.