BIZTRAC BETA
Landscape service activities

APELAND VEDLIKEHOLD AS

Org. no. 923479708 Limited company (AS) Stavanger Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 179,000
Operating profit NOK −113,000
Equity NOK −299,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−299k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−113k kr).

APELAND VEDLIKEHOLD AS is registered as a limited company in Stavanger, Rogaland with organisation number 923479708. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Vedlikehold av uteområder, mindre entreprenør oppdrag og salg av ved.”. The most recent filed accounts, for the 2024 financial year, show NOK 179,000 in revenue and NOK −113,000 in operating profit.

Key figures · 2024

Revenue
NOK 179,000
Operating profit
NOK −113,000
Equity
NOK −299,000

Financial health · 2024

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

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

Who owns APELAND VEDLIKEHOLD AS?

No shareholders are registered for APELAND VEDLIKEHOLD AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about APELAND VEDLIKEHOLD AS

What is the revenue of APELAND VEDLIKEHOLD AS?

APELAND VEDLIKEHOLD AS had revenue of NOK 179,000 in 2024.

Who is the general manager of APELAND VEDLIKEHOLD AS?

Agnar Apeland is registered as general manager of APELAND VEDLIKEHOLD AS.

Where is APELAND VEDLIKEHOLD AS based?

APELAND VEDLIKEHOLD AS has its business address in Rennesøy.

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.