biztrac. BETA
COMPANY REGISTER PROFILE
925243701 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other non-specialised retail sale

OSS2 AS

Org. no. 925243701 Limited company (AS) Haugesund Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK −137,000
Equity NOK 240,000
Incorporated 2020
Employees 6
Share capital NOK 30,000

Signals

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

OSS2 AS is registered as a limited company in Haugesund, Rogaland with organisation number 925243701. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 2020 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av detaljvarer gjennom butikk, samt drive annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK −137,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
▼ −7 %
Operating profit
NOK −137,000
▼ −108 %
Equity
NOK 240,000
▼ −58 %
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
1.44
Satisfactory
Current assets ÷ current liabilities
Profitability
-18.1%
Not satisfactory
Return on total assets
Solidity
38.5%
Good
Equity as a share of total capital

Who owns OSS2 AS?

OSS2 AS
NOK 4.0m rev. · NOK −137,000 profit

OSS2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSS2 AS

Who owns OSS2 AS?

Hege Romerheim is the largest registered owner, with 100.0%.

What is the revenue of OSS2 AS?

OSS2 AS had revenue of NOK 4.0m in 2025.

Who is the general manager of OSS2 AS?

Hege Romerheim is registered as general manager of OSS2 AS.

Where is OSS2 AS based?

OSS2 AS has its business address in Haugesund.

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.