BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

HENRIKSEN & RYMOEN AS

Org. no. 934230043 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 78
Operating profit NOK 78
Equity NOK 45,000
Incorporated 2024
Share capital NOK 45,000

HENRIKSEN & RYMOEN AS is registered as a limited company in Oslo, Oslo with organisation number 934230043. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2024. Registered share capital is NOK 45,000, divided into 1500 shares. The company's stated purpose is: “Kalibrering av TV-er. Kalibrering av TV vil si at vi tilpasser farger og lys som kommer fra panelet på en TV, til lysforholdene som TV-en oppholder seg i. Dette gjøres med bruk av profesjonelle verktøy fra ekstern leverandør.”. The most recent filed accounts, for the 2024 financial year, show NOK 78 in revenue and NOK 78 in operating profit.

Key figures · 2024

Revenue
NOK 78
Operating profit
NOK 78
Equity
NOK 45,000
Est. value
NOK 22,000

Financial health · 2024

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 HENRIKSEN & RYMOEN AS?

TIM-ANDRÉ HENRIKSEN
HENRIKSEN & RYMOEN AS
NOK 78 rev. · NOK 78 profit

HENRIKSEN & RYMOEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HENRIKSEN & RYMOEN AS

Who owns HENRIKSEN & RYMOEN AS?

TIM-ANDRÉ HENRIKSEN is the largest registered owner, with 66.7%.

What is the revenue of HENRIKSEN & RYMOEN AS?

HENRIKSEN & RYMOEN AS had revenue of NOK 78 in 2024.

Where is HENRIKSEN & RYMOEN AS based?

HENRIKSEN & RYMOEN 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.