BIZTRAC BETA
Rental and operating of own or leased real estate

LEIRVIKÅSEN 45 AS

Org. no. 921399049 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 5.0m
Operating profit NOK 3.1m
Equity NOK 5.7m
Incorporated 2018
Share capital NOK 2.0m

LEIRVIKÅSEN 45 AS is registered as a limited company in Bergen, Vestland with organisation number 921399049. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 2.0m, divided into 2000000 shares. The company's stated purpose is: “Investere i eiendom og andre selskaper og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.0m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 5.0m
Operating profit
NOK 3.1m
Equity
NOK 5.7m
Est. value
NOK 10.2m

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.0%
Good
Equity as a share of total capital

Who owns LEIRVIKÅSEN 45 AS?

LAFI HOLDING AS
LEIRVIKÅSEN 45 AS
NOK 5.0m rev. · NOK 3.1m profit

LEIRVIKÅSEN 45 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEIRVIKÅSEN 45 AS

Who owns LEIRVIKÅSEN 45 AS?

LAFI HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LEIRVIKÅSEN 45 AS?

LEIRVIKÅSEN 45 AS had revenue of NOK 5.0m in 2024.

Who is the general manager of LEIRVIKÅSEN 45 AS?

Pål Edvardsen is registered as general manager of LEIRVIKÅSEN 45 AS.

Where is LEIRVIKÅSEN 45 AS based?

LEIRVIKÅSEN 45 AS has its business address in Godvik.

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.