BIZTRAC BETA
Architectural activities

EIKA LANDSKAP AS

Org. no. 922107726 Limited company (AS) Stavanger Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK −477,000
Equity NOK −86,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−86k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−477k kr).

EIKA LANDSKAP AS is registered as a limited company in Stavanger, Rogaland with organisation number 922107726. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulenttjenester innenfor landskapsarkitektur.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK −477,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK −477,000
Equity
NOK −86,000

Financial health · 2025

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

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

Who owns EIKA LANDSKAP AS?

Astrid Norland
EIKA LANDSKAP AS
NOK 2.3m rev. · NOK −477,000 profit

EIKA LANDSKAP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EIKA LANDSKAP AS

Who owns EIKA LANDSKAP AS?

Astrid Norland is the largest registered owner, with 80.0%.

What is the revenue of EIKA LANDSKAP AS?

EIKA LANDSKAP AS had revenue of NOK 2.3m in 2025.

Who is the general manager of EIKA LANDSKAP AS?

Astrid Norland is registered as general manager of EIKA LANDSKAP AS.

Where is EIKA LANDSKAP AS based?

EIKA LANDSKAP AS has its business address in Stavanger.

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.