biztrac. BETA
COMPANY REGISTER PROFILE
932618931 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Retail sale of clothing

THEOSOL AS

Org. no. 932618931 Limited company (AS) Stavanger Incorporated 2023 Active
Revenue 2025 NOK 1.8m
Operating profit NOK −220,000
Equity NOK −230,000
Incorporated 2023
Employees 10
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−230k kr).

THEOSOL AS is registered as a limited company in Stavanger, Rogaland with organisation number 932618931. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2023 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg av brukt barnetøy.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK −220,000 in operating profit.

Former names: JOLLY AS

Key figures · 2025

Revenue
NOK 1.8m
▲ +3 %
Operating profit
NOK −220,000
▼ −600 %
Equity
NOK −230,000
▼ −2328 %

Financial health · 2025

Liquidity
0.31
Not satisfactory
Current assets ÷ current liabilities
Profitability
-90.6%
Not satisfactory
Return on total assets
Solidity
-134.5%
Weak
Equity as a share of total capital

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

Who owns THEOSOL AS?

THEOSOL AS
NOK 1.8m rev. · NOK −220,000 profit

THEOSOL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about THEOSOL AS

Who owns THEOSOL AS?

Hanne Sofie Næss Breistein is the largest registered owner, with 100.0%.

What is the revenue of THEOSOL AS?

THEOSOL AS had revenue of NOK 1.8m in 2025.

Who is the general manager of THEOSOL AS?

Hanne Sofie Næss Breistein is registered as general manager of THEOSOL AS.

Where is THEOSOL AS based?

THEOSOL 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.