BIZTRAC BETA
COMPANY REGISTER PROFILE
990391637 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

SYNNE OG MORFAR AS

Org. no. 990391637 Limited company (AS) Asker Incorporated 2006 Active
Ownership graph ↗
Equity NOK 595,000
Incorporated 2006
Share capital NOK 250,000

SYNNE OG MORFAR AS is registered as a limited company in Asker, Akershus with organisation number 990391637. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2006. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Drive aktiv kapitalforvaltning, samt alt som står i forbindelse med dette, herunder deltakelse i andre selskaper med lignende formål.”.

Key figures · 2025

Equity
NOK 595,000
▲ +10 %
Est. value
NOK 669,000

Financial health · 2025

Liquidity
618.96
Very good
Current assets ÷ current liabilities
Profitability
9.8%
Satisfactory
Return on total assets
Solidity
99.8%
Very good
Equity as a share of total capital

Who owns SYNNE OG MORFAR AS?

SYNNE OG MORFAR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SYNNE OG MORFAR AS

Who owns SYNNE OG MORFAR AS?

SYNNE KVAMME is the largest registered owner, with 99.6%.

Who is the general manager of SYNNE OG MORFAR AS?

Ole Ekroll Sørdahl is registered as general manager of SYNNE OG MORFAR AS.

Where is SYNNE OG MORFAR AS based?

SYNNE OG MORFAR AS has its business address in Nesbru.

Property

Business address Bloksbergstien 19, 1394 Nesbru
Cadastral unit 3203-39/1945/0/0
Building Enebolig · 1 unit

12 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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