BIZTRAC BETA
Rental and operating of own or leased real estate

HEDDALSVEGEN 23 NOTODDEN AS

Org. no. 918607366 Limited company (AS) Larvik Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 735,000
Equity NOK 171,000
Incorporated 2017
Share capital NOK 46,000

HEDDALSVEGEN 23 NOTODDEN AS is registered as a limited company in Larvik, Vestfold with organisation number 918607366. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 46,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom samt eiendomsutvikling. Eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 735,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 735,000
Equity
NOK 171,000
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
0.33
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.1%
Satisfactory
Equity as a share of total capital

Who owns HEDDALSVEGEN 23 NOTODDEN AS?

SOLO BOLIG TELEMARK AS
HEDDALSVEGEN 23 NOTODDEN AS
NOK 2.2m rev. · NOK 735,000 profit

HEDDALSVEGEN 23 NOTODDEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEDDALSVEGEN 23 NOTODDEN AS

Who owns HEDDALSVEGEN 23 NOTODDEN AS?

SOLO BOLIG TELEMARK AS is the largest registered owner, with 100.0%.

What is the revenue of HEDDALSVEGEN 23 NOTODDEN AS?

HEDDALSVEGEN 23 NOTODDEN AS had revenue of NOK 2.2m in 2025.

Where is HEDDALSVEGEN 23 NOTODDEN AS based?

HEDDALSVEGEN 23 NOTODDEN AS has its business address in Larvik.

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.