BIZTRAC BETA
Development of building projects

ESG23 AS

Org. no. 916930372 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK 64,000
Equity NOK −3.7m
Incorporated 2016
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−3,7 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ESG23 AS is registered as a limited company in Oslo, Oslo with organisation number 916930372. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Eiendomsutvikling, kjøp og salg av eiendom og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2025

Operating profit
NOK 64,000
Equity
NOK −3.7m
Est. value
NOK 494,000

Financial health · 2025

Liquidity
1.80
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-190.8%
Weak
Equity as a share of total capital

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

Who owns ESG23 AS?

PROSJEKTSELSKAP PDT17 AS
ESG23 AS
· NOK 64,000 profit

ESG23 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ESG23 AS own?

ESG23 AS holds a stake in 1 company:

See the full ownership structure →

Group structure

ESG23 AS er morselskap for 19 datterselskaper:

Frequently asked questions about ESG23 AS

Who owns ESG23 AS?

PROSJEKTSELSKAP PDT17 AS is the largest registered owner, with 100.0%.

Where is ESG23 AS based?

ESG23 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 15.06.2026.

Report a problem

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