biztrac. BETA
COMPANY REGISTER PROFILE
921416180 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other non-specialised retail sale

BULK HOLDING AS

Org. no. 921416180 Limited company (AS) Oslo Incorporated 2018 Active
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2018
Share capital NOK 110,000

BULK HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 921416180. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 2018. Registered share capital is NOK 110,000, divided into 1000 shares. The company's stated purpose is: “Holdingselskap.”. 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
▲ +100 %
Equity
NOK 24,000
▲ +0 %
Est. value
NOK 31,000

Financial health · 2025

Liquidity
0.57
Weak
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
Return on total assets
Solidity
65.7%
Weak
Equity as a share of total capital

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

Who owns BULK HOLDING AS?

BULK HOLDING AS
NOK 0 rev. · NOK 0 profit

BULK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BULK HOLDING AS own?

BULK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BULK HOLDING AS

Who owns BULK HOLDING AS?

Alexander Ulvestad Hjermind is the largest registered owner, with 100.0%.

What is the revenue of BULK HOLDING AS?

BULK HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of BULK HOLDING AS?

Alexander Ulvestad Hjermind is registered as general manager of BULK HOLDING AS.

Where is BULK HOLDING AS based?

BULK HOLDING 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.