BIZTRAC BETA
Business and other management consultancy activities

SKIPTA AS

Org. no. 915839606 Limited company (AS) Øksnes Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 91,000
Operating profit NOK −55,000
Equity NOK 18.3m
Incorporated 2015
Share capital NOK 930,000

Signals

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

SKIPTA AS is registered as a limited company in Øksnes, Nordland with organisation number 915839606. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2015. Registered share capital is NOK 930,000, divided into 30000 shares. The company's stated purpose is: “Rådgivning og konsulenttjenester samt å delta i andre selskap som aksjeeier, gjennom investeringer eller på annen måte. I tillegg gjøre bruk av finansielle instrumenter herunder kjøp og salg av valuta og omløpsaksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 91,000 in revenue and NOK −55,000 in operating profit.

Key figures · 2025

Revenue
NOK 91,000
Operating profit
NOK −55,000
Equity
NOK 18.3m
Est. value
NOK 22.8m

Financial health · 2025

Liquidity
3343.28
Very good
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 SKIPTA AS?

STIAN FRIVÅG
SKIPTA AS
NOK 91,000 rev. · NOK −55,000 profit

SKIPTA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKIPTA AS

Who owns SKIPTA AS?

STIAN FRIVÅG is the largest registered owner, with 100.0%.

What is the revenue of SKIPTA AS?

SKIPTA AS had revenue of NOK 91,000 in 2025.

Who is the general manager of SKIPTA AS?

Stian Frivåg is registered as general manager of SKIPTA AS.

Where is SKIPTA AS based?

SKIPTA AS has its business address in Myre.

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.