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

OLIVER OG FARFAR AS

Org. no. 919784423 Limited company (AS) Asker Incorporated 2017 Active
Ownership graph ↗
Equity NOK 345,000
Incorporated 2017
Share capital NOK 250,000

OLIVER OG FARFAR AS is registered as a limited company in Asker, Akershus with organisation number 919784423. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “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 345,000
▲ +14 %
Est. value
NOK 452,000

Financial health · 2025

Liquidity
410.99
Very good
Current assets ÷ current liabilities
Profitability
11.4%
Good
Return on total assets
Solidity
87.1%
Very good
Equity as a share of total capital

Who owns OLIVER OG FARFAR AS?

OLIVER OG FARFAR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLIVER OG FARFAR AS

Who owns OLIVER OG FARFAR AS?

OLE EKROLL SØRDAHL is the largest registered owner, with 0.4%.

Who is the general manager of OLIVER OG FARFAR AS?

Ole Ekroll Sørdahl is registered as general manager of OLIVER OG FARFAR AS.

Where is OLIVER OG FARFAR AS based?

OLIVER OG FARFAR 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.