BIZTRAC BETA
Business and other management consultancy activities

VALIANT EIENDOM AS

Org. no. 965387463 Limited company (AS) Oslo Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 778,000
Operating profit NOK 529,000
Equity NOK 4.4m
Incorporated 1992
Share capital NOK 120,000

VALIANT EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 965387463. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1992. Registered share capital is NOK 120,000, divided into 2400 shares. The company's stated purpose is: “Erverve fast eiendom, aksjer og andre verdipapirer og samleobjekter som frimerker, mynter og lignende, samt å investere i andre selskap med økonomisk formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 778,000 in revenue and NOK 529,000 in operating profit.

Key figures · 2024

Revenue
NOK 778,000
Operating profit
NOK 529,000
Equity
NOK 4.4m
Est. value
NOK 4.4m

Financial health · 2024

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

Who owns VALIANT EIENDOM AS?

BIRGIT MARIE BJØRNDAL LIODDEN
VALIANT EIENDOM AS
NOK 778,000 rev. · NOK 529,000 profit

VALIANT EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VALIANT EIENDOM AS own?

VALIANT EIENDOM AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about VALIANT EIENDOM AS

Who owns VALIANT EIENDOM AS?

BIRGIT MARIE BJØRNDAL LIODDEN is the largest registered owner, with 100.0%.

What is the revenue of VALIANT EIENDOM AS?

VALIANT EIENDOM AS had revenue of NOK 778,000 in 2024.

Where is VALIANT EIENDOM AS based?

VALIANT EIENDOM 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 15.06.2026.

Report a problem

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