biztrac. BETA
COMPANY REGISTER PROFILE
922853576 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

RINGHUS HOLDING AS

Org. no. 922853576 Limited company (AS) Vinje Incorporated 2019 Active
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 139,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

RINGHUS HOLDING AS is registered as a limited company in Vinje, Telemark with organisation number 922853576. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eige aksjer, fast eigendom, maskiner, kjøp og salg av maskiner og delta i andre virksomheter, samt virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
▲ +12 %
Equity
NOK 139,000
▼ −25 %
Est. value
NOK 127,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-6.4%
Not satisfactory
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns RINGHUS HOLDING AS?

RINGHUS HOLDING AS
NOK 0 rev. · NOK −10,000 profit

RINGHUS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RINGHUS HOLDING AS

Who owns RINGHUS HOLDING AS?

Emil Botne Ringhus is the largest registered owner, with 100.0%.

What is the revenue of RINGHUS HOLDING AS?

RINGHUS HOLDING AS had revenue of NOK 0 in 2025.

Where is RINGHUS HOLDING AS based?

RINGHUS HOLDING AS has its business address in Vinje.

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.