BIZTRAC BETA
Accounting and bookkeeping

FOSSEN REGNSKAP AS

Org. no. 994527096 Limited company (AS) Indre Østfold Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −185,000
Equity NOK 24,000
Incorporated 2009
Share capital NOK 30,000

Signals

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

FOSSEN REGNSKAP AS is registered as a limited company in Indre Østfold, Østfold with organisation number 994527096. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2009. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Virke som autorisert regnskapsførerselskap, føre regnskap for andre.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −185,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −185,000
Equity
NOK 24,000
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
1.13
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FOSSEN REGNSKAP AS?

GRY HELENE KARTERUD
FOSSEN REGNSKAP AS
NOK 1.1m rev. · NOK −185,000 profit

FOSSEN REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOSSEN REGNSKAP AS

Who owns FOSSEN REGNSKAP AS?

GRY HELENE KARTERUD is the largest registered owner, with 100.0%.

What is the revenue of FOSSEN REGNSKAP AS?

FOSSEN REGNSKAP AS had revenue of NOK 1.1m in 2025.

Who is the general manager of FOSSEN REGNSKAP AS?

Gry Helene Karterud is registered as general manager of FOSSEN REGNSKAP AS.

Where is FOSSEN REGNSKAP AS based?

FOSSEN REGNSKAP AS has its business address in Tomter.

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.