BIZTRAC BETA
Rental and operating of own or leased real estate

ASSET 23 AS

Org. no. 923735615 Limited company (AS) Porsgrunn Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −405,000
Equity NOK −7.4m
Incorporated 2019
Share capital NOK 30,000

Signals

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

ASSET 23 AS is registered as a limited company in Porsgrunn, Telemark with organisation number 923735615. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie fast eiendom, eiendomsutvikling og utleie av fast eiendom, eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”.

Key figures · 2025

Operating profit
NOK −405,000
Equity
NOK −7.4m

Financial health · 2025

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-5.5%
Weak
Equity as a share of total capital

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

Who owns ASSET 23 AS?

PROSPECTIVE AS
ASSET 23 AS
· NOK −405,000 profit

ASSET 23 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ASSET 23 AS own?

ASSET 23 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ASSET 23 AS

Who owns ASSET 23 AS?

PROSPECTIVE AS is the largest registered owner, with 100.0%.

Where is ASSET 23 AS based?

ASSET 23 AS has its business address in Porsgrunn.

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.