BIZTRAC BETA
COMPANY REGISTER PROFILE
912131653 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other business support service activities n.e.c.

PRESTENGA UTVIKLING AS

Org. no. 912131653 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Operating profit NOK 2.4m
Equity NOK −6.3m
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−6,3 mill kr).

PRESTENGA UTVIKLING AS is registered as a limited company in Oslo, Oslo with organisation number 912131653. The business is classified under other business support service activities n.e.c. (NACE 82.990). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulentvirksomhet, handel, agentur, eie, drive og selge fast eiendom. Utleie av fast eiendom og driftsmidler, samt engasjement i andre selskaper samt hva som står i forbindelse med dette. Entreprenørvirksomhet.”.

Key figures · 2025

Operating profit
NOK 2.4m
▲ +2628 %
Equity
NOK −6.3m
▲ +23 %
Est. value
NOK 13.0m

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
689.2%
Very good
Return on total assets
Solidity
-12494.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns PRESTENGA UTVIKLING AS?

PRESTENGA UTVIKLING AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about PRESTENGA UTVIKLING AS

Who owns PRESTENGA UTVIKLING AS?

BERBERE GROUP AS is the largest registered owner, with 25.0%.

Who is the general manager of PRESTENGA UTVIKLING AS?

Tom-Espen Grunnteig is registered as general manager of PRESTENGA UTVIKLING AS.

Where is PRESTENGA UTVIKLING AS based?

PRESTENGA UTVIKLING AS has its business address in Oslo.

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.