BIZTRAC BETA
COMPANY REGISTER PROFILE
922753911 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

RAEDERGAARD HOLDING AS

Org. no. 922753911 Limited company (AS) Tynset Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 166,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

RAEDERGAARD HOLDING AS is registered as a limited company in Tynset, Innlandet with organisation number 922753911. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer og andre verdigjenstander og hertilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 166,000
Est. value
NOK 973,000

Financial health · 2025

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

Who owns RAEDERGAARD HOLDING AS?

RAEDERGAARD HOLDING AS
NOK 0 rev. · NOK −6,000 profit

RAEDERGAARD HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RAEDERGAARD HOLDING AS

Who owns RAEDERGAARD HOLDING AS?

RUNE RÆDERGÅRD is the largest registered owner, with 66.7%.

What is the revenue of RAEDERGAARD HOLDING AS?

RAEDERGAARD HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of RAEDERGAARD HOLDING AS?

Rune Rædergård is registered as general manager of RAEDERGAARD HOLDING AS.

Where is RAEDERGAARD HOLDING AS based?

RAEDERGAARD HOLDING AS has its business address in Tynset.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 25.08.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.