BIZTRAC BETA
Rental and operating of own or leased real estate

KROMMENIE AS

Org. no. 982982723 Limited company (AS) Kristiansand Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 1.3m
Equity NOK 24.0m
Incorporated 2001
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-02-09 Adresseendring registrert 2026-02-09.

KROMMENIE AS is registered as a limited company in Kristiansand, Agder with organisation number 982982723. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Varesalg og konsulentarbeid samt investeringer i fast eiendom, finansobjekter og deltagelse i andre selskaper samt annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 1.3m
Equity
NOK 24.0m
Est. value
NOK 19.9m

Financial health · 2024

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

Who owns KROMMENIE AS?

ØYVIND LAUVLAND
KROMMENIE AS
NOK 1.5m rev. · NOK 1.3m profit

KROMMENIE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KROMMENIE AS own?

KROMMENIE AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about KROMMENIE AS

Who owns KROMMENIE AS?

ØYVIND LAUVLAND is the largest registered owner, with 100.0%.

What is the revenue of KROMMENIE AS?

KROMMENIE AS had revenue of NOK 1.5m in 2024.

Where is KROMMENIE AS based?

KROMMENIE AS has its business address in Kristiansand S.

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.