biztrac. BETA
COMPANY REGISTER PROFILE
819530912 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

HVIDSTEN INVEST AS

Org. no. 819530912 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 16,000
Incorporated 2017
Share capital NOK 30,000

HVIDSTEN INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 819530912. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer, eiendom og andre eierandeler, samt tilsvarende og annen type virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 16,000
▲ +0 %
Est. value
NOK 14,000

Financial health · 2025

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

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

Who owns HVIDSTEN INVEST AS?

HVIDSTEN INVEST AS
NOK 0 rev. · NOK 0 profit

HVIDSTEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HVIDSTEN INVEST AS own?

HVIDSTEN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HVIDSTEN INVEST AS

Who owns HVIDSTEN INVEST AS?

Nicolay Holmedahl Hvidsten is the largest registered owner, with 100.0%.

What is the revenue of HVIDSTEN INVEST AS?

HVIDSTEN INVEST AS had revenue of NOK 0 in 2025.

Where is HVIDSTEN INVEST AS based?

HVIDSTEN INVEST AS has its business address in Oslo.

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.