BIZTRAC BETA
Rental and operating of own or leased real estate

HEGDALVEIEN 65 AS

Org. no. 934104293 Limited company (AS) Larvik Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 2.1m
Equity NOK 4.2m
Incorporated 2024
Share capital NOK 259,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-04-11 Adresseendring registrert 2026-04-11.

HEGDALVEIEN 65 AS is registered as a limited company in Larvik, Vestfold with organisation number 934104293. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 259,000, divided into 1000 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 2.3m in revenue and NOK 2.1m in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 2.1m
Equity
NOK 4.2m
Est. value
NOK 7.1m

Financial health · 2025

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

Who owns HEGDALVEIEN 65 AS?

TROLLBORG EIENDOM VESTFOLD AS
HEGDALVEIEN 65 AS
NOK 2.3m rev. · NOK 2.1m profit

HEGDALVEIEN 65 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEGDALVEIEN 65 AS

Who owns HEGDALVEIEN 65 AS?

TROLLBORG EIENDOM VESTFOLD AS is the largest registered owner, with 100.0%.

What is the revenue of HEGDALVEIEN 65 AS?

HEGDALVEIEN 65 AS had revenue of NOK 2.3m in 2025.

Where is HEGDALVEIEN 65 AS based?

HEGDALVEIEN 65 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.