BIZTRAC BETA
Business and other management consultancy activities

SUELO AS

Org. no. 889125802 Limited company (AS) Bærum Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 261,000
Equity NOK 36.9m
Incorporated 2005
Share capital NOK 100,000

SUELO AS is registered as a limited company in Bærum, Akershus with organisation number 889125802. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og forvalte aksjer, obligasjoner og andre verdipapirer, eie og forvalte eiendom, deltagelse i andre selskaper, utøvelse av rådgivnings- og konsulentvirksomhet, samt hva som står i forbindelse hermed.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 261,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 261,000
Equity
NOK 36.9m
Est. value
NOK 19.7m

Financial health · 2024

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

Who owns SUELO AS?

KJETIL BAKKE ERIKSEN
SUELO AS
NOK 1.6m rev. · NOK 261,000 profit

SUELO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SUELO AS own?

SUELO AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SUELO AS

Who owns SUELO AS?

KJETIL BAKKE ERIKSEN is the largest registered owner, with 100.0%.

What is the revenue of SUELO AS?

SUELO AS had revenue of NOK 1.6m in 2024.

Who is the general manager of SUELO AS?

Kjetil Bakke Eriksen is registered as general manager of SUELO AS.

Where is SUELO AS based?

SUELO AS has its business address in Fornebu.

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.