BIZTRAC BETA
Uoppgitt

FOXHOUND HOLDING AS

Org. no. 925741124 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −20,000
Equity NOK 724,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−20k kr).
  • Nylig endring 2026-04-09 Adresseendring registrert 2026-04-09.

FOXHOUND HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 925741124. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom. Investering i verdipapirer. Selskapet kan også delta i annen næringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −20,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −20,000
Equity
NOK 724,000
Est. value
NOK 5.0m

Financial health · 2024

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

Who owns FOXHOUND HOLDING AS?

CHRISTOFFER FRAURUD
FOXHOUND HOLDING AS
NOK 0 rev. · NOK −20,000 profit

FOXHOUND HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FOXHOUND HOLDING AS own?

FOXHOUND HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FOXHOUND HOLDING AS

Who owns FOXHOUND HOLDING AS?

CHRISTOFFER FRAURUD is the largest registered owner, with 100.0%.

What is the revenue of FOXHOUND HOLDING AS?

FOXHOUND HOLDING AS had revenue of NOK 0 in 2024.

Where is FOXHOUND HOLDING AS based?

FOXHOUND 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 15.06.2026.

Report a problem

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