BIZTRAC BETA
Rental and operating of own or leased real estate

LEIRVIKÅSEN 35 AS

Org. no. 980363090 Limited company (AS) Bergen Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 5.4m
Operating profit NOK 3.1m
Equity NOK 1.6m
Incorporated 1998
Share capital NOK 697,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LEIRVIKÅSEN 35 AS is registered as a limited company in Bergen, Vestland with organisation number 980363090. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1998. Registered share capital is NOK 697,000, divided into 696669 shares. The company's stated purpose is: “Drift av eiendommer, herunder kjøp og salg, samt øvrige aktiviteter.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.4m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 5.4m
Operating profit
NOK 3.1m
Equity
NOK 1.6m
Est. value
NOK 7.9m

Financial health · 2024

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

Who owns LEIRVIKÅSEN 35 AS?

LAFI HOLDING AS
LEIRVIKÅSEN 35 AS
NOK 5.4m rev. · NOK 3.1m profit

LEIRVIKÅSEN 35 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEIRVIKÅSEN 35 AS

Who owns LEIRVIKÅSEN 35 AS?

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

What is the revenue of LEIRVIKÅSEN 35 AS?

LEIRVIKÅSEN 35 AS had revenue of NOK 5.4m in 2024.

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

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

Where is LEIRVIKÅSEN 35 AS based?

LEIRVIKÅSEN 35 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.