Skip to main content
Greencoat Renewables Plc logo

Greencoat Renewables Plc — Investor Relations & Filings

Ticker · GRP ISIN · IE00BF2NR112 LEI · 635400TVSIFFQOB8RB67 IR Electricity, gas, steam and air conditioning supply
Open in API
Filings indexed 1,046 across all filing types
Latest filing 2024-06-27 Transaction in Own Shar…
Country IE Ireland
Listing IR GRP

About Greencoat Renewables Plc

https://www.greencoat-renewables.com/

Greencoat Renewables Plc is an investment company that acquires, owns, and operates renewable energy infrastructure assets. The company manages a portfolio of over 40 operational sites across several European markets, with an installed net capacity exceeding 1.5GW. Its assets include onshore and offshore wind farms, solar PV, and battery storage facilities. The core business involves generating clean electricity, which is sold to the grid and directly to corporate customers through Power Purchase Agreements (PPAs). The company focuses on using cash generated from operations to provide stable returns to shareholders via dividends and to reinvest in its portfolio to support the energy transition.

Recent filings

Filing Released Lang Actions
Transaction in Own Shares
Transaction in Own Shares Classification · 100% confidence The document explicitly states its purpose in the title section: 'Greencoat Renewables PLC ... Transaction in Own Shares'. It details the number of ordinary shares purchased on a specific date (26 June 2024) as part of a share buyback programme, including prices and volume-weighted averages. This directly corresponds to the definition of 'Transaction in Own Shares' (Code: POS), which covers company buying back or selling its own shares (share repurchase/issuance). The presence of the RNS Number and the closing statement confirms it is a regulatory announcement, but the specific content dictates the POS classification over the general RNS fallback.
2024-06-27 English
Transaction in Own Shares
Transaction in Own Shares Classification · 100% confidence The document explicitly states 'Transaction in Own Shares' and details the purchase and cancellation of Ordinary Shares as part of a 'share buyback programme'. This directly corresponds to the definition of a company buying back or selling its own shares. The appropriate filing type code is POS (Transaction in Own Shares). The document is short and contains the full details, so it is not an RPA.
2024-06-26 English
Transaction in Own Shares
Transaction in Own Shares Classification · 100% confidence The document explicitly states the subject is 'Transaction in Own Shares' and details the purchase of a specific number of Ordinary Shares on a specific date (June 25, 2024) as part of a share buyback programme. This directly corresponds to the definition of 'Transaction in Own Shares' (Code: POS). The presence of the RNS Number and the closing statement about RNS being the news service of the London Stock Exchange confirms it is a regulatory announcement, but the specific content dictates the POS classification over the general RNS fallback.
2024-06-26 English
Transaction in Own Shares
Environmental & Social Information Classification · 89% confidence The document text provided is extremely short, truncated, and appears to be metadata or the beginning of a structured document, possibly an XML or JSON structure, given the 'author', 'date', 'processor', and 'status' fields, followed by a base64 encoded image tag and then a very small snippet of text that looks like the start of a financial document or presentation. The document snippet itself contains: 1. A reference to a processor ('python-docx+mammoth'). 2. A base64 image tag. 3. A few lines of text that look like a partial transcript or notes, mentioning names (Catherine Carron) and dates. 4. The actual document text snippet is too fragmented to definitively classify as a full report (like 10-K or IR). It contains fragments of dialogue or notes that resemble a Call Transcript (CT) or perhaps an Investor Presentation (IP) if it were longer. However, the key rule here is the 'MENU VS MEAL' rule: If a document is very short and seems to be an announcement or wrapper, it should be classified as RPA or RNS. Given the structure (metadata header) and the very short, fragmented content, this is most likely an announcement about a filing or a very brief regulatory update, rather than the full content of a major report. Since the content is too sparse to fit specific categories like 10-K, ER, or IR, and it doesn't explicitly announce a report release (like RPA), the most appropriate fallback for a miscellaneous, short, or incomplete filing structure is Regulatory Filings (RNS). Revisiting the context: The provided text is highly structured metadata followed by a tiny, unclassifiable text body. This strongly suggests the system is processing a file wrapper or a very brief regulatory notice that doesn't contain substantial financial data. RNS is the best general fallback for regulatory notices that don't fit elsewhere.
2024-06-25 English
Transaction in Own Shares
Transaction in Own Shares Classification · 100% confidence The document explicitly states its subject matter as 'Transaction in Own Shares' and details the purchase and cancellation of Ordinary Shares as part of a share buyback programme. This directly corresponds to the definition of 'Transaction in Own Shares' (Code: POS). Although it is distributed via RNS, the specific content dictates the POS classification over the general RNS fallback. The document length (4664 chars) is not short enough to trigger the RPA/RNS rule based on announcing an attached report, as this document contains the substantive transaction details itself.
2024-06-25 English
Transaction in Own Shares
Environmental & Social Information Classification · 89% confidence The document text provided is extremely short, truncated, and appears to be metadata or the beginning of a structured document (indicated by 'author', 'date', 'processor', 'status'). Crucially, the document length is 28,974 characters, which is substantial enough to be a full report, but the provided text snippet is very sparse and contains no clear regulatory headers (like 10-K, AR, DEF 14A) or explicit financial reporting language typical of comprehensive reports (like 10-K or IR). The text snippet itself does not contain the full content of a report, but rather seems to be an introduction or header section. However, the provided text snippet contains a mix of names, dates, and technical processing information, followed by a very short excerpt of what looks like a financial discussion or Q&A transcript, including references to specific financial results and shareholder votes (e.g., 'shareholder votes', 'financial results'). The excerpt mentions specific financial figures and discussions typical of an earnings call or management discussion. Let's re-evaluate based on the provided definitions and the 'MENU VS MEAL' rule: 1. The document length (28,974 chars) suggests it is a full report, not just an announcement. 2. The content excerpt, although fragmented, discusses specific financial outcomes and shareholder interactions (implied by the Q&A style in the final part, although the final part is heavily truncated and seems to be from a different context/document based on the structure). Given the highly fragmented nature of the provided text, which seems to mix metadata with a snippet of a financial discussion, I must rely on the most common indicators if the full context is unavailable. The final lines show a Q&A structure related to financial performance and shareholder actions, which strongly suggests a Call Transcript (CT) or perhaps an Earnings Release (ER) if it were just the highlights. Let's look closely at the final lines: - Mentions of specific financial outcomes (e.g., 'shareholder votes', 'financial results'). - The structure resembles a Q&A session (e.g., 'Q: ... A: ...'). - The context seems to be a discussion following a financial event. If this were a full document, the length suggests it's not just an RPA. Since the content snippet strongly hints at spoken discussion and Q&A following results, Call Transcript (CT) is the most plausible classification for the *type* of content being sampled, assuming the full document is indeed a transcript. If the document were a full 10-K or IR, the text would be dense with formal section headings and detailed tables, which are absent here. Given the strong indication of spoken dialogue/Q&A in the final lines, I classify this as a Call Transcript (CT).
2024-06-24 English

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.