BIZTRAC BETA
Accounting and bookkeeping

SKAGERAK ØKONOMIPARTNER AS

Org. no. 924676833 Limited company (AS) Sandefjord Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 5.2m
Operating profit NOK 228,000
Equity NOK 1.1m
Incorporated 2020
Employees 5
Share capital NOK 100,000

SKAGERAK ØKONOMIPARTNER AS is registered as a limited company in Sandefjord, Vestfold with organisation number 924676833. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2020 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Regnskapsføring, konsulenttjenester innen IT, økonomi/skatt og utleie av arbeidskraft, samt deltagelse i andre selskaper som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.2m in revenue and NOK 228,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.2m
Operating profit
NOK 228,000
Equity
NOK 1.1m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns SKAGERAK ØKONOMIPARTNER AS?

SKAGERAK CONSULTING AS
SKAGERAK ØKONOMIPARTNER AS
NOK 5.2m rev. · NOK 228,000 profit

SKAGERAK ØKONOMIPARTNER AS has 3 registered shareholders:

All shareholders and roles →

Group structure

SKAGERAK ØKONOMIPARTNER AS er morselskap for 2 datterselskaper:

Frequently asked questions about SKAGERAK ØKONOMIPARTNER AS

Who owns SKAGERAK ØKONOMIPARTNER AS?

SKAGERAK CONSULTING AS is the largest registered owner, with 60.0%.

What is the revenue of SKAGERAK ØKONOMIPARTNER AS?

SKAGERAK ØKONOMIPARTNER AS had revenue of NOK 5.2m in 2025.

Where is SKAGERAK ØKONOMIPARTNER AS based?

SKAGERAK ØKONOMIPARTNER AS has its business address in Stokke.

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.