biztrac. BETA
COMPANY REGISTER PROFILE
934872959 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

ROHUMYR HOLDING AS

Org. no. 934872959 Limited company (AS) Tromsø Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 21,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

ROHUMYR HOLDING AS is registered as a limited company in Tromsø, Troms with organisation number 934872959. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 21,000
Est. value
NOK 39,000

Financial health · 2025

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

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

Who owns ROHUMYR HOLDING AS?

ROHUMYR HOLDING AS
NOK 0 rev. · NOK −9,000 profit

ROHUMYR HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ROHUMYR HOLDING AS own?

ROHUMYR HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ROHUMYR HOLDING AS

Who owns ROHUMYR HOLDING AS?

Rolf-Hugo Myrseth is the largest registered owner, with 100.0%.

What is the revenue of ROHUMYR HOLDING AS?

ROHUMYR HOLDING AS had revenue of NOK 0 in 2025.

Where is ROHUMYR HOLDING AS based?

ROHUMYR HOLDING AS has its business address in Krokelvdalen.

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.