BIZTRAC BETA
Accounting and bookkeeping

SYNNØVE BERGERSEN AS

Org. no. 989259954 Limited company (AS) Elverum Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK −2,000
Equity NOK 440,000
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2k kr).

SYNNØVE BERGERSEN AS is registered as a limited company in Elverum, Innlandet with organisation number 989259954. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive regnskapsførsel og rådgiving, herunder deltagelse i andre selskaper samt hva som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK −2,000
Equity
NOK 440,000
Est. value
NOK 2.2m

Financial health · 2024

Liquidity
1.85
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
46.5%
Very good
Equity as a share of total capital

Who owns SYNNØVE BERGERSEN AS?

SYNNØVE BERGERSEN
SYNNØVE BERGERSEN AS
NOK 1.9m rev. · NOK −2,000 profit

SYNNØVE BERGERSEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SYNNØVE BERGERSEN AS

Who owns SYNNØVE BERGERSEN AS?

SYNNØVE BERGERSEN is the largest registered owner, with 90.0%.

What is the revenue of SYNNØVE BERGERSEN AS?

SYNNØVE BERGERSEN AS had revenue of NOK 1.9m in 2024.

Who is the general manager of SYNNØVE BERGERSEN AS?

Synnøve Bergersen is registered as general manager of SYNNØVE BERGERSEN AS.

Where is SYNNØVE BERGERSEN AS based?

SYNNØVE BERGERSEN AS has its business address in Elverum.

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.