BIZTRAC BETA
Business and other management consultancy activities

SAEL CONSULTING AS

Org. no. 813886162 Limited company (AS) Stavanger Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −55,000
Equity NOK −522,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

SAEL CONSULTING AS is registered as a limited company in Stavanger, Rogaland with organisation number 813886162. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulentvirksomhet innen ledelse, investering/eierskap i potensielle vekstselskaper. Styredeltagelse i potensielle vekstselskaper.”.

Key figures · 2025

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

Financial health · 2025

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

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

Who owns SAEL CONSULTING AS?

EGIL SÆL
SAEL CONSULTING AS
· NOK −55,000 profit

SAEL CONSULTING AS has 6 registered shareholders:

All shareholders and roles →

Which companies does SAEL CONSULTING AS own?

SAEL CONSULTING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SAEL CONSULTING AS

Who owns SAEL CONSULTING AS?

EGIL SÆL is the largest registered owner, with 52.0%.

Who is the general manager of SAEL CONSULTING AS?

Egil Sæl is registered as general manager of SAEL CONSULTING AS.

Where is SAEL CONSULTING AS based?

SAEL CONSULTING AS has its business address in Stavanger.

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.