biztrac. BETA
COMPANY REGISTER PROFILE
913156323 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Accounting and bookkeeping

ONSØY REGNSKAP AS

Org. no. 913156323 Limited company (AS) Fredrikstad Incorporated 2014 Active
Revenue 2025 NOK 10.7m
Operating profit NOK 739,000
Equity NOK 2.1m
Incorporated 2014
Employees 9
Share capital NOK 300,000

ONSØY REGNSKAP AS is registered as a limited company in Fredrikstad, Østfold with organisation number 913156323. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2014 and has 9 registered employees. Registered share capital is NOK 300,000, divided into 30 shares. The company's stated purpose is: “Føre regnskap for andre, samt økonomisk rådgivning og annen bistand som naturlig hører med til regnskapsoppdragene.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.7m in revenue and NOK 739,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.7m
▲ +0 %
Operating profit
NOK 739,000
▼ −36 %
Equity
NOK 2.1m
▼ −14 %
Est. value
NOK 5.0m

Financial health · 2025

Liquidity
1.55
Good
Current assets ÷ current liabilities
Profitability
14.0%
Good
Return on total assets
Solidity
38.5%
Good
Equity as a share of total capital

Who owns ONSØY REGNSKAP AS?

ONSØY REGNSKAP AS
NOK 10.7m rev. · NOK 739,000 profit

ONSØY REGNSKAP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ONSØY REGNSKAP AS

Who owns ONSØY REGNSKAP AS?

Arne Ingar Bossum is the largest registered owner, with 73.3%.

What is the revenue of ONSØY REGNSKAP AS?

ONSØY REGNSKAP AS had revenue of NOK 10.7m in 2025.

Who is the general manager of ONSØY REGNSKAP AS?

Arne Ingar Bossum is registered as general manager of ONSØY REGNSKAP AS.

Where is ONSØY REGNSKAP AS based?

ONSØY REGNSKAP AS has its business address in Gressvik.

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

Report a problem

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