BIZTRAC BETA
Uoppgitt

BALTHAZAR AS

Org. no. 933724522 Limited company (AS) Porsgrunn Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 22,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

BALTHAZAR AS is registered as a limited company in Porsgrunn, Telemark with organisation number 933724522. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering aksjer og andre verdipapirer, investering i fast eiendom og andre formuesgjenstander, samt annen virksomhet som står i nær sammenheng med dette. Drive konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 22,000
Est. value
NOK 26,000

Financial health · 2024

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

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

Who owns BALTHAZAR AS?

VLADIMIR VLADIMIROVICH ODINOKOV
BALTHAZAR AS
NOK 0 rev. · NOK −8,000 profit

BALTHAZAR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BALTHAZAR AS own?

BALTHAZAR AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BALTHAZAR AS

Who owns BALTHAZAR AS?

VLADIMIR VLADIMIROVICH ODINOKOV is the largest registered owner, with 100.0%.

What is the revenue of BALTHAZAR AS?

BALTHAZAR AS had revenue of NOK 0 in 2025.

Where is BALTHAZAR AS based?

BALTHAZAR AS has its business address in Porsgrunn.

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.