BIZTRAC BETA
COMPANY REGISTER PROFILE
990006679 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Non-specialised wholesale trade

SKI-PEER AS

Org. no. 990006679 Limited company (AS) Østre Toten Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 5.8m
Operating profit NOK −262,000
Equity NOK 4.4m
Incorporated 2006
Employees 5
Share capital NOK 100,000

Signals

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

SKI-PEER AS is registered as a limited company in Østre Toten, Innlandet with organisation number 990006679. The business is classified under non-specialised wholesale trade (NACE 46.900). The company was incorporated in 2006 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av varer og tjenester, samt hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.8m in revenue and NOK −262,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.8m
▲ +0 %
Operating profit
NOK −262,000
▲ +58 %
Equity
NOK 4.4m
▼ −4 %
Est. value
NOK 4.0m

Financial health · 2025

Liquidity
4.03
Very good
Current assets ÷ current liabilities
Profitability
-3.5%
Not satisfactory
Return on total assets
Solidity
79.5%
Very good
Equity as a share of total capital

Who owns SKI-PEER AS?

SKI-PEER AS
NOK 5.8m rev. · NOK −262,000 profit

SKI-PEER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SKI-PEER AS

Who owns SKI-PEER AS?

TORMOD ALM is the largest registered owner, with 70.0%.

What is the revenue of SKI-PEER AS?

SKI-PEER AS had revenue of NOK 5.8m in 2025.

Who is the general manager of SKI-PEER AS?

Tormod Alm is registered as general manager of SKI-PEER AS.

Where is SKI-PEER AS based?

SKI-PEER AS has its business address in Kapp.

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

Report a problem

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