biztrac. BETA
COMPANY REGISTER PROFILE
933878074 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

HVERVEN UTVIKLING AS

Org. no. 933878074 Limited company (AS) Holmestrand Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK 13,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

HVERVEN UTVIKLING AS is registered as a limited company in Holmestrand, Vestfold with organisation number 933878074. 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 30,000, divided into 300 shares. The company's stated purpose is: “Investering i, drift og utleie av eiendom, konsulenttjenester og annen virksomhet knyttet til dette.”.

Key figures · 2025

Operating profit
NOK −9,000
▼ −304167 %
Equity
NOK 13,000
▼ −41 %
Est. value
NOK 12,000

Financial health · 2025

Liquidity
2.52
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
60.3%
Weak
Equity as a share of total capital

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

Who owns HVERVEN UTVIKLING AS?

HVERVEN UTVIKLING AS
· NOK −9,000 profit

HVERVEN UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

HVERVEN UTVIKLING AS er morselskap for 2 datterselskaper:

Frequently asked questions about HVERVEN UTVIKLING AS

Who owns HVERVEN UTVIKLING AS?

HVERVEN HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of HVERVEN UTVIKLING AS?

Jan Kristian Hverven is registered as general manager of HVERVEN UTVIKLING AS.

Where is HVERVEN UTVIKLING AS based?

HVERVEN UTVIKLING AS has its business address in Sande I Vestfold.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.