BIZTRAC BETA
Business and other management consultancy activities

EGERS AS

Org. no. 997823532 Limited company (AS) Tønsberg Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 51,000
Equity NOK 206,000
Incorporated 2012
Share capital NOK 30,000

EGERS AS is registered as a limited company in Tønsberg, Vestfold with organisation number 997823532. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kommersiell utvikling og drift av forretningsideer og prosjekter innen handel, kjøpesenter og eiendom, herunder konsulentvirksomhet, samt investering og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 51,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 51,000
Equity
NOK 206,000
Est. value
NOK 336,000

Financial health · 2025

Liquidity
0.32
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.3%
Good
Equity as a share of total capital

Who owns EGERS AS?

PÅL GRABOW BAKKE EGELAND
EGERS AS
NOK 1.0m rev. · NOK 51,000 profit

EGERS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EGERS AS own?

EGERS AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about EGERS AS

Who owns EGERS AS?

PÅL GRABOW BAKKE EGELAND is the largest registered owner, with 100.0%.

What is the revenue of EGERS AS?

EGERS AS had revenue of NOK 1.0m in 2025.

Who is the general manager of EGERS AS?

Pål Grabow Bakke Egeland is registered as general manager of EGERS AS.

Where is EGERS AS based?

EGERS AS has its business address in Tønsberg.

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.