BIZTRAC BETA
Rental and operating of own or leased real estate

LAVIK EIGENDOM AS

Org. no. 932688891 Limited company (AS) Høyanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 339,000
Operating profit NOK 225
Equity NOK −223,000
Incorporated 2023
Share capital NOK 90,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−223k kr).

LAVIK EIGENDOM AS is registered as a limited company in Høyanger, Vestland with organisation number 932688891. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 90,000, divided into 90000 shares. The company's stated purpose is: “Drive med utleige av egen eller leid fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 339,000 in revenue and NOK 225 in operating profit.

Key figures · 2025

Revenue
NOK 339,000
Operating profit
NOK 225
Equity
NOK −223,000
Est. value
NOK 2,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LAVIK EIGENDOM AS?

BJØRN INGE SYSTAD
LAVIK EIGENDOM AS
NOK 339,000 rev. · NOK 225 profit

LAVIK EIGENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about LAVIK EIGENDOM AS

Who owns LAVIK EIGENDOM AS?

BJØRN INGE SYSTAD is the largest registered owner, with 25.0%.

What is the revenue of LAVIK EIGENDOM AS?

LAVIK EIGENDOM AS had revenue of NOK 339,000 in 2025.

Who is the general manager of LAVIK EIGENDOM AS?

Reinert Jensen is registered as general manager of LAVIK EIGENDOM AS.

Where is LAVIK EIGENDOM AS based?

LAVIK EIGENDOM AS has its business address in Lavik.

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.