BIZTRAC BETA
Rental and operating of own or leased real estate

E LØNNING AS

Org. no. 984570775 Limited company (AS) Bømlo Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 226,000
Operating profit NOK 20,000
Equity NOK 29.3m
Incorporated 2002
Share capital NOK 1.5m

E LØNNING AS is registered as a limited company in Bømlo, Vestland with organisation number 984570775. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 1.5m, divided into 15000 shares. The company's stated purpose is: “Erverv av fast eiendom og foreta utleie av denne, drive mottak, foredling og omsetning av fiskeprdoukter, grossistvirksomhet, handel, eksport, import, samt hva hermed står i forbindelse, herunder å delta i andre foretagender som driver tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 226,000 in revenue and NOK 20,000 in operating profit.

Key figures · 2024

Revenue
NOK 226,000
Operating profit
NOK 20,000
Equity
NOK 29.3m
Est. value
NOK 20.3m

Financial health · 2024

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

Who owns E LØNNING AS?

EIVIND LØNNING
E LØNNING AS
NOK 226,000 rev. · NOK 20,000 profit

E LØNNING AS has 5 registered shareholders:

All shareholders and roles →

Which companies does E LØNNING AS own?

E LØNNING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about E LØNNING AS

Who owns E LØNNING AS?

EIVIND LØNNING is the largest registered owner, with 53.7%.

What is the revenue of E LØNNING AS?

E LØNNING AS had revenue of NOK 226,000 in 2024.

Where is E LØNNING AS based?

E LØNNING AS has its business address in Bømlo.

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.