BIZTRAC BETA
Other non-specialised retail sale

FURNES SKI & SPORT AS

Org. no. 961970539 Limited company (AS) Ringsaker Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 786,000
Incorporated 1991
Share capital NOK 100,000

Signals

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

FURNES SKI & SPORT AS is registered as a limited company in Ringsaker, Innlandet with organisation number 961970539. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 1991. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Handel, selskapet kan ved aksjetegning eller på annen måte ha eierinteresser i andre foretak.”. 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
Equity
NOK 786,000
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns FURNES SKI & SPORT AS?

AAGE HØIBY
FURNES SKI & SPORT AS
NOK 0 rev. · NOK −10,000 profit

FURNES SKI & SPORT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FURNES SKI & SPORT AS own?

FURNES SKI & SPORT AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FURNES SKI & SPORT AS

Who owns FURNES SKI & SPORT AS?

AAGE HØIBY is the largest registered owner, with 100.0%.

What is the revenue of FURNES SKI & SPORT AS?

FURNES SKI & SPORT AS had revenue of NOK 0 in 2025.

Where is FURNES SKI & SPORT AS based?

FURNES SKI & SPORT AS has its business address in Brumunddal.

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.