BIZTRAC BETA
Business and other management consultancy activities

ROES AS

Org. no. 991200614 Limited company (AS) Hol Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −28,000
Equity NOK 213,000
Incorporated 2007
Share capital NOK 100,000

Signals

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

ROES AS is registered as a limited company in Hol, Buskerud with organisation number 991200614. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investere i andre virksomheter gjennom aksjer eller på annen måte, samt salg av konsulenttjenester og virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −28,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −28,000
Equity
NOK 213,000
Est. value
NOK 384,000

Financial health · 2025

Liquidity
4.96
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
82.5%
Very good
Equity as a share of total capital

Who owns ROES AS?

ROGER ESPELI
ROES AS
NOK 0 rev. · NOK −28,000 profit

ROES AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ROES AS own?

ROES AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ROES AS

Who owns ROES AS?

ROGER ESPELI is the largest registered owner, with 100.0%.

What is the revenue of ROES AS?

ROES AS had revenue of NOK 0 in 2025.

Who is the general manager of ROES AS?

Roger Espeli is registered as general manager of ROES AS.

Where is ROES AS based?

ROES AS has its business address in Geilo.

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.