BIZTRAC BETA
Development of building projects

TRE EKER AS

Org. no. 922859922 Limited company (AS) Frogn Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −2,000
Equity NOK −151,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

TRE EKER AS is registered as a limited company in Frogn, Akershus with organisation number 922859922. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Erverve, utvikle, drive og avhende fast eiendom, samt annen naturlig tilhørende virksomhet. Selskapet kan eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK −151,000

Financial health · 2024

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

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

Who owns TRE EKER AS?

RETIRO AS
TRE EKER AS
NOK 0 rev. · NOK −2,000 profit

TRE EKER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRE EKER AS

Who owns TRE EKER AS?

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

What is the revenue of TRE EKER AS?

TRE EKER AS had revenue of NOK 0 in 2024.

Where is TRE EKER AS based?

TRE EKER AS has its business address in Drøbak.

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.