BIZTRAC BETA
Other captive investment companies

EML AS

Org. no. 997761979 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 100,000
Operating profit NOK −6,000
Equity NOK 5.5m
Incorporated 2011
Share capital NOK 159,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

EML AS is registered as a limited company in Oslo, Oslo with organisation number 997761979. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2011. Registered share capital is NOK 159,000, divided into 158625 shares. The company's stated purpose is: “Være et inveseteringsselskap, herunder gjennom investeringer i finansielle instrumenter, aksjer, obligasjoner og andre låneinstrumenter, andeler i selskap etter selskapsloven, eiendom og andre finaniselle instrumenter og eiendeler, og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 100,000 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 100,000
Operating profit
NOK −6,000
Equity
NOK 5.5m
Est. value
NOK 7.7m

Financial health · 2025

Liquidity
763.38
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
77.9%
Very good
Equity as a share of total capital

Who owns EML AS?

PETER LØVAAS
EML AS
NOK 100,000 rev. · NOK −6,000 profit

EML AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EML AS own?

EML AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about EML AS

Who owns EML AS?

PETER LØVAAS is the largest registered owner, with 100.0%.

What is the revenue of EML AS?

EML AS had revenue of NOK 100,000 in 2025.

Where is EML AS based?

EML AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.