biztrac. BETA
COMPANY REGISTER PROFILE
925038431 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

ESTENE AS

Org. no. 925038431 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK −52,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−52k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

ESTENE AS is registered as a limited company in Bærum, Akershus with organisation number 925038431. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer, eiendom og andre eierandeler, samt tilsvarende og annen type virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
▲ +66 %
Equity
NOK −52,000
▼ −8 %

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
-4.4%
Not satisfactory
Return on total assets
Solidity
-54.0%
Weak
Equity as a share of total capital

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

Who owns ESTENE AS?

ESTENE AS
NOK 0 rev. · NOK −4,000 profit

ESTENE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ESTENE AS own?

ESTENE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ESTENE AS

Who owns ESTENE AS?

Even Risan Stene is the largest registered owner, with 100.0%.

What is the revenue of ESTENE AS?

ESTENE AS had revenue of NOK 0 in 2025.

Where is ESTENE AS based?

ESTENE AS has its business address in Haslum.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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