biztrac. BETA
COMPANY REGISTER PROFILE
982793122 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

PROLOG AS

Org. no. 982793122 Limited company (AS) Asker Incorporated 2000 Active
Revenue 2025 NOK 1.3m
Operating profit NOK 255,000
Equity NOK 40.5m
Incorporated 2000
Share capital NOK 5.1m

PROLOG AS is registered as a limited company in Asker, Akershus with organisation number 982793122. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2000. Registered share capital is NOK 5.1m, divided into 9110 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder deltakelse i andre selskaper. Konsulentvirksomhet innen dagligvarer. Salg, markedsføring, strategi og forretningsutvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 255,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
▼ −14 %
Operating profit
NOK 255,000
▼ −66 %
Equity
NOK 40.5m
▲ +1 %
Est. value
NOK 21.4m

Financial health · 2025

Liquidity
18.46
Very good
Current assets ÷ current liabilities
Profitability
6.8%
Satisfactory
Return on total assets
Solidity
94.6%
Very good
Equity as a share of total capital

Who owns PROLOG AS?

PROLOG AS has 4 registered shareholders:

All shareholders and roles →

Which companies does PROLOG AS own?

PROLOG AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about PROLOG AS

Who owns PROLOG AS?

Anders Fjeld is the largest registered owner, with 48.9%.

What is the revenue of PROLOG AS?

PROLOG AS had revenue of NOK 1.3m in 2025.

Who is the general manager of PROLOG AS?

Åsmund Rødseth Fjeld is registered as general manager of PROLOG AS.

Where is PROLOG AS based?

PROLOG AS has its business address in Asker.

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.