biztrac. BETA
COMPANY REGISTER PROFILE
930688800 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Pre-primary education

VELLE EIENDOM II AS

Org. no. 930688800 Limited company (AS) Tønsberg Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 545,000
Equity NOK 1.4m
Incorporated 2022
Share capital NOK 30,000

VELLE EIENDOM II AS is registered as a limited company in Tønsberg, Vestfold with organisation number 930688800. The business is classified under pre-primary education (NACE 85.100). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie og drive fast eiendom og dertil hørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 545,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
▲ +2 %
Operating profit
NOK 545,000
▼ −6 %
Equity
NOK 1.4m
▲ +7 %
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns VELLE EIENDOM II AS?

VELLE EIENDOM II AS
NOK 1.2m rev. · NOK 545,000 profit

VELLE EIENDOM II AS has 1 registered shareholder:

All shareholders and roles →

Group structure

VELLE EIENDOM II AS er morselskap for 7 datterselskaper:

Frequently asked questions about VELLE EIENDOM II AS

Who owns VELLE EIENDOM II AS?

VELLE GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of VELLE EIENDOM II AS?

VELLE EIENDOM II AS had revenue of NOK 1.2m in 2025.

Who is the general manager of VELLE EIENDOM II AS?

Siv Hjertø is registered as general manager of VELLE EIENDOM II AS.

Where is VELLE EIENDOM II AS based?

VELLE EIENDOM II 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 03.10.2026.

Report a problem

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