BIZTRAC BETA
Repair and maintenance of motor vehicles

ESPEN ØSTBY AS

Org. no. 912506193 Limited company (AS) Nesodden Incorporated 2013 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK −55,000
Incorporated 2013
Share capital NOK 30,000

Signals

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

ESPEN ØSTBY AS is registered as a limited company in Nesodden, Akershus with organisation number 912506193. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringer i aksjer, fast eiendom og alt som naturlig faller inn under dette.”.

Key figures · 2025

Operating profit
NOK −9,000
Equity
NOK −55,000

Financial health · 2025

Liquidity
-0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-191.2%
Weak
Equity as a share of total capital

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

Who owns ESPEN ØSTBY AS?

ESPEN ØSTBY
ESPEN ØSTBY AS
· NOK −9,000 profit

ESPEN ØSTBY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ESPEN ØSTBY AS own?

ESPEN ØSTBY AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ESPEN ØSTBY AS

Who owns ESPEN ØSTBY AS?

ESPEN ØSTBY is the largest registered owner, with 100.0%.

Who is the general manager of ESPEN ØSTBY AS?

Espen Østby is registered as general manager of ESPEN ØSTBY AS.

Where is ESPEN ØSTBY AS based?

ESPEN ØSTBY AS has its business address in Fjellstrand.

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.