Welcome!

News Feed Item

Changes in the Number of Shares and Votes in Lundin Petroleum AB

STOCKHOLM, SWEDEN -- (Marketwired) -- 05/30/14 -- Reference is made to the press release dated 15 May 2014 regarding the Annual General Meeting of Lundin Petroleum AB's (TSX: LUP)(OMX: LUPE) ("Lundin Petroleum") resolutions to reduce the company's share capital through cancellation of shares held in treasury and to increase the company's share capital through a bonus issue.

The reduction of the company's share capital with an amount of SEK 68,402.50 through cancellation of 6,840,250 shares held in treasury recently conducted by Lundin Petroleum has resulted in the following changes in the number of shares and votes in the company during May 2014.

Prior to the reduction of the company's share capital through cancellation of shares held in treasury, there were in total 317,910,580 shares and votes in Lundin Petroleum of which 8,840,250 were held in treasury by Lundin Petroleum. As a result of the cancellation, the number of shares and votes decreased by 6,840,250. Thus, following the cancellation, there are, as of 30 May 2014, 311,070,330 shares and votes in the company, of which 2,000,000 are held in treasury by Lundin Petroleum.

In accordance with the resolution of the Annual General Meeting, the reduction of share capital through cancellation of shares held in treasury was followed by an increase of the company's share capital with an amount of SEK 68,402.50 through a bonus issue in order to restore the company's share capital after the reduction. Thus, the cancelation of shares held in treasury has not affected the company's share capital that still amounts to SEK 3,179,105.80.

Lundin Petroleum is a Swedish independent oil and gas exploration and production company with a well balanced portfolio of world-class assets primarily located in Europe and South East Asia. The Company is listed at the NASDAQ OMX, Stockholm (ticker "LUPE") and at the Toronto Stock Exchange (TSX) (Ticker "LUP"). Lundin Petroleum has proven and probable reserves of 194 million barrels of oil equivalent (MMboe).

This information has been made public in accordance with the Securities Market Act (SFS 2007:528) and/or the Financial Instruments Trading Act (SFS 1991:980).

Forward-Looking Statements

Certain statements made and information contained herein constitute "forward-looking information" (within the meaning of applicable securities legislation). Such statements and information (together, "forward-looking statements") relate to future events, including the Company's future performance, business prospects or opportunities. Forward-looking statements include, but are not limited to, statements with respect to estimates of reserves and/or resources, future production levels, future capital expenditures and their allocation to exploration and development activities, future drilling and other exploration and development activities. Ultimate recovery of reserves or resources are based on forecasts of future results, estimates of amounts not yet determinable and assumptions of management.

All statements other than statements of historical fact may be forward-looking statements. Statements concerning proven and probable reserves and resource estimates may also be deemed to constitute forward-looking statements and reflect conclusions that are based on certain assumptions that the reserves and resources can be economically exploited. Any statements that express or involve discussions with respect to predictions, expectations, beliefs, plans, projections, objectives, assumptions or future events or performance (often, but not always, using words or phrases such as "seek", "anticipate", "plan", "continue", "estimate", "expect", "may", "will", "project", "predict", "potential", "targeting", "intend", "could", "might", "should", "believe" and similar expressions) are not statements of historical fact and may be "forward-looking statements". Forward-looking statements involve known and unknown risks, uncertainties and other factors that may cause actual results or events to differ materially from those anticipated in such forward-looking statements. No assurance can be given that these expectations and assumptions will prove to be correct and such forward-looking statements should not be relied upon. These statements speak only as on the date of the information and the Company does not intend, and does not assume any obligation, to update these forward-looking statements, except as required by applicable laws. These forward-looking statements involve risks and uncertainties relating to, among other things, operational risks (including exploration and development risks), productions costs, availability of drilling equipment, reliance on key personnel, reserve estimates, health, safety and environmental issues, legal risks and regulatory changes, competition, geopolitical risk, and financial risks. These risks and uncertainties are described in more detail under the heading "Risks and Risk Management" and elsewhere in the Company's annual report. Readers are cautioned that the foregoing list of risk factors should not be construed as exhaustive. Actual results may differ materially from those expressed or implied by such forward-looking statements. Forward-looking statements are expressly qualified by this cautionary statement.

Reserves and Resources

Unless otherwise stated, Lundin Petroleum's reserve and resource estimates are as at 31 December 2013, and have been prepared and audited in accordance with National Instrument 51-101 Standards of Disclosure for Oil and Gas Activities ("NI 51-101") and the Canadian Oil and Gas Evaluation Handbook ("COGE Handbook"). Unless otherwise stated, all reserves estimates contained herein are the aggregate of "Proved Reserves" and "Probable Reserves", together also known as "2P Reserves". For further information on reserve and resource classifications, see "Reserves, Resources and Production" in the Company's annual report.

Contingent Resources

Contingent Resources are those quantities of petroleum estimated, as of a given date, to be potentially recoverable from known accumulations using established technology or technology under development, but are not currently considered to be commercially recoverable due to one or more contingencies. Contingencies may include factors such as economic, legal, environmental, political and regulatory matters or a lack of markets. There is no certainty that it will be commercially viable for the Company to produce any portion of the Contingent Resources. . Unless otherwise stated, all contingent resource estimates contained herein are the best estimate ("2C") contingent resources.

Prospective Resources

Prospective Resources are those quantities of petroleum estimated, as of a given date, to be potentially recoverable from undiscovered accumulations by application of future development projects. Prospective Resources have both a chance of discovery and a chance of development. There is no certainty that any portion of the Prospective Resources will be discovered. If discovered, there is no certainty that it will be commercially viable to produce any portion of the Prospective Resources. Unless otherwise stated, all Prospective Resource estimates contained herein are reflecting a P50 Prospective Resource estimate. Risked Prospective Resources reported herein are partially risked. They have been risked for chance of discovery, but have not been risked for chance of development.

BOEs

BOEs may be misleading, particularly if used in isolation. A BOE conversion ratio of 6 Mcf : 1 Bbl is based on an energy equivalency conversion method primarily applicable at the burner tip and does not represent a value equivalency at the wellhead.

More Stories By Marketwired .

Copyright © 2009 Marketwired. All rights reserved. All the news releases provided by Marketwired are copyrighted. Any forms of copying other than an individual user's personal reference without express written permission is prohibited. Further distribution of these materials is strictly forbidden, including but not limited to, posting, emailing, faxing, archiving in a public database, redistributing via a computer network or in a printed form.

Latest Stories
WebRTC has had a real tough three or four years, and so have those working with it. Only a few short years ago, the development world were excited about WebRTC and proclaiming how awesome it was. You might have played with the technology a couple of years ago, only to find the extra infrastructure requirements were painful to implement and poorly documented. This probably left a bitter taste in your mouth, especially when things went wrong.
Up until last year, enterprises that were looking into cloud services usually undertook a long-term pilot with one of the large cloud providers, running test and dev workloads in the cloud. With cloud’s transition to mainstream adoption in 2015, and with enterprises migrating more and more workloads into the cloud and in between public and private environments, the single-provider approach must be revisited. In his session at 18th Cloud Expo, Yoav Mor, multi-cloud solution evangelist at Cloudy...
When you focus on a journey from up-close, you look at your own technical and cultural history and how you changed it for the benefit of the customer. This was our starting point: too many integration issues, 13 SWP days and very long cycles. It was evident that in this fast-paced industry we could no longer afford this reality. We needed something that would take us beyond reducing the development lifecycles, CI and Agile methodologies. We made a fundamental difference, even changed our culture...
The proper isolation of resources is essential for multi-tenant environments. The traditional approach to isolate resources is, however, rather heavyweight. In his session at 18th Cloud Expo, Igor Drobiazko, co-founder of elastic.io, drew upon his own experience with operating a Docker container-based infrastructure on a large scale and present a lightweight solution for resource isolation using microservices. He also discussed the implementation of microservices in data and application integrat...
All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and containers together help companies achieve their business goals faster and more effectively. In his session at DevOps Summit, Ruslan Synytsky, CEO and Co-founder of Jelastic, reviewed the current landscape of Dev...
In his General Session at DevOps Summit, Asaf Yigal, Co-Founder & VP of Product at Logz.io, will explore the value of Kibana 4 for log analysis and will give a real live, hands-on tutorial on how to set up Kibana 4 and get the most out of Apache log files. He will examine three use cases: IT operations, business intelligence, and security and compliance. This is a hands-on session that will require participants to bring their own laptops, and we will provide the rest.
IoT is at the core or many Digital Transformation initiatives with the goal of re-inventing a company's business model. We all agree that collecting relevant IoT data will result in massive amounts of data needing to be stored. However, with the rapid development of IoT devices and ongoing business model transformation, we are not able to predict the volume and growth of IoT data. And with the lack of IoT history, traditional methods of IT and infrastructure planning based on the past do not app...
"LinearHub provides smart video conferencing, which is the Roundee service, and we archive all the video conferences and we also provide the transcript," stated Sunghyuk Kim, CEO of LinearHub, in this SYS-CON.tv interview at @ThingsExpo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
"We're bringing out a new application monitoring system to the DevOps space. It manages large enterprise applications that are distributed throughout a node in many enterprises and we manage them as one collective," explained Kevin Barnes, President of eCube Systems, in this SYS-CON.tv interview at DevOps at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York City, NY.
With major technology companies and startups seriously embracing IoT strategies, now is the perfect time to attend @ThingsExpo 2016 in New York. Learn what is going on, contribute to the discussions, and ensure that your enterprise is as "IoT-Ready" as it can be! Internet of @ThingsExpo, taking place June 6-8, 2017, at the Javits Center in New York City, New York, is co-located with 20th Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry p...
@DevOpsSummit at Cloud taking place June 6-8, 2017, at Javits Center, New York City, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to wait for long developm...
In a recent research, analyst firm IDC found that the average cost of a critical application failure is $500,000 to $1 million per hour and the average total cost of unplanned application downtime is $1.25 billion to $2.5 billion per year for Fortune 1000 companies. In addition to the findings on the cost of the downtime, the research also highlighted best practices for development, testing, application support, infrastructure, and operations teams.
Updating DevOps to the latest production data slows down your development cycle. Probably it is due to slow, inefficient conventional storage and associated copy data management practices. In his session at @DevOpsSummit at 20th Cloud Expo, Dhiraj Sehgal, in Product and Solution at Tintri, will talk about DevOps and cloud-focused storage to update hundreds of child VMs (different flavors) with updates from a master VM in minutes, saving hours or even days in each development cycle. He will also...
"There's a growing demand from users for things to be faster. When you think about all the transactions or interactions users will have with your product and everything that is between those transactions and interactions - what drives us at Catchpoint Systems is the idea to measure that and to analyze it," explained Leo Vasiliou, Director of Web Performance Engineering at Catchpoint Systems, in this SYS-CON.tv interview at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York Ci...