BIZTRAC BETA
Uoppgitt

EGE AS

Org. no. 828599542 Limited company (AS) Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 96,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

EGE AS is registered as a limited company in Hå, Rogaland with organisation number 828599542. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 96,000
Est. value
NOK 113,000

Financial health · 2025

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

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

Who owns EGE AS?

RUBEN EGE
EGE AS
NOK 0 rev. · NOK −6,000 profit

EGE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EGE AS own?

EGE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about EGE AS

Who owns EGE AS?

RUBEN EGE is the largest registered owner, with 100.0%.

What is the revenue of EGE AS?

EGE AS had revenue of NOK 0 in 2025.

Who is the general manager of EGE AS?

Ruben Ege is registered as general manager of EGE AS.

Where is EGE AS based?

EGE AS has its business address in Nærbø.

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.