BIZTRAC BETA
Business and other management consultancy activities

ULYSSES AS

Org. no. 999134106 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 5.4m
Operating profit NOK 1.1m
Equity NOK 35,000
Incorporated 2012
Share capital NOK 35,000

ULYSSES AS is registered as a limited company in Oslo, Oslo with organisation number 999134106. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2012. Registered share capital is NOK 35,000, divided into 350 shares. The company's stated purpose is: “Drive konsulent, undervisning og investeringsvirksomhet, herunder eie aksjer i andre selskaper, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.4m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 5.4m
Operating profit
NOK 1.1m
Equity
NOK 35,000
Est. value
NOK 4.3m

Financial health · 2024

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

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

Who owns ULYSSES AS?

STEINAR BJARTVEIT
ULYSSES AS
NOK 5.4m rev. · NOK 1.1m profit

ULYSSES AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ULYSSES AS own?

ULYSSES AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ULYSSES AS

Who owns ULYSSES AS?

STEINAR BJARTVEIT is the largest registered owner, with 67.1%.

What is the revenue of ULYSSES AS?

ULYSSES AS had revenue of NOK 5.4m in 2024.

Who is the general manager of ULYSSES AS?

Steinar Bjartveit is registered as general manager of ULYSSES AS.

Where is ULYSSES AS based?

ULYSSES AS has its business address in Oslo.

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.