BIZTRAC BETA
Rental and operating of own or leased real estate

SVARTADALEN AS

Org. no. 986484531 Limited company (AS) Lier Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 813,000
Equity NOK 4.8m
Incorporated 2004
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SVARTADALEN AS is registered as a limited company in Lier, Buskerud with organisation number 986484531. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 813,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 813,000
Equity
NOK 4.8m
Est. value
NOK 4.8m

Financial health · 2025

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.3%
Good
Equity as a share of total capital

Who owns SVARTADALEN AS?

TESS VEST EIENDOM AS
SVARTADALEN AS
NOK 1.3m rev. · NOK 813,000 profit

SVARTADALEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SVARTADALEN AS

Who owns SVARTADALEN AS?

TESS VEST EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of SVARTADALEN AS?

SVARTADALEN AS had revenue of NOK 1.3m in 2025.

Who is the general manager of SVARTADALEN AS?

Erlend Gjerdevik is registered as general manager of SVARTADALEN AS.

Where is SVARTADALEN AS based?

SVARTADALEN AS has its business address in Lierstranda.

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.