BIZTRAC BETA
COMPANY REGISTER PROFILE
932835967 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

LAUVIK AS

Org. no. 932835967 Limited company (AS) Øygarden Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK 129,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

LAUVIK AS is registered as a limited company in Øygarden, Vestland with organisation number 932835967. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom.”.

Key figures · 2025

Operating profit
NOK −4,000
▼ −418 %
Equity
NOK 129,000
▲ +452 %
Est. value
NOK 484,000

Financial health · 2025

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

Who owns LAUVIK AS?

LAUVIK AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LAUVIK AS own?

LAUVIK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LAUVIK AS

Who owns LAUVIK AS?

METTE EIDE LAUVIK is the largest registered owner, with 50.0%.

Where is LAUVIK AS based?

LAUVIK AS has its business address in Ågotnes.

Property

Business address Rekkjavegen 20, 5363 Ågotnes
Cadastral unit 4626-20/145/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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