BIZTRAC BETA
Buying and selling of own real estate

HOVLANDVEIEN 6 HOLDING AS

Org. no. 931472895 Limited company (AS) Tønsberg Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 564,000
Operating profit NOK 471,000
Equity NOK −3.9m
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−3,9 mill kr).

HOVLANDVEIEN 6 HOLDING AS is registered as a limited company in Tønsberg, Vestfold with organisation number 931472895. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i aksjer og fast eiendom og hva hermed står i forbindelse, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 564,000 in revenue and NOK 471,000 in operating profit.

Key figures · 2025

Revenue
NOK 564,000
Operating profit
NOK 471,000
Equity
NOK −3.9m
Est. value
NOK 2.8m

Financial health · 2025

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

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

Who owns HOVLANDVEIEN 6 HOLDING AS?

N.K BYGG AS
HOVLANDVEIEN 6 HOLDING AS
NOK 564,000 rev. · NOK 471,000 profit

HOVLANDVEIEN 6 HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HOVLANDVEIEN 6 HOLDING AS

Who owns HOVLANDVEIEN 6 HOLDING AS?

N.K BYGG AS is the largest registered owner, with 50.0%.

What is the revenue of HOVLANDVEIEN 6 HOLDING AS?

HOVLANDVEIEN 6 HOLDING AS had revenue of NOK 564,000 in 2025.

Where is HOVLANDVEIEN 6 HOLDING AS based?

HOVLANDVEIEN 6 HOLDING AS has its business address in Tønsberg.

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.