biztrac. BETA
COMPANY REGISTER PROFILE
988929824 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

OS INVEST AS

Org. no. 988929824 Limited company (AS) Bjørnafjorden Incorporated 2005 Active
Revenue 2025 NOK 1.3m
Operating profit NOK 220,000
Equity NOK −227,000
Incorporated 2005
Share capital NOK 200,000

Signals

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

OS INVEST AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 988929824. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Kjøp, restaurering, drift og salg av eiendommer, vikar og konsulenttjenester samt kjøp og salg av verdipapir.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 220,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
▲ +30 %
Operating profit
NOK 220,000
▲ +516 %
Equity
NOK −227,000
▲ +37 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
1.11
Satisfactory
Current assets ÷ current liabilities
Profitability
9.6%
Satisfactory
Return on total assets
Solidity
-9.3%
Weak
Equity as a share of total capital

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

Who owns OS INVEST AS?

OS INVEST AS
NOK 1.3m rev. · NOK 220,000 profit

OS INVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OS INVEST AS

Who owns OS INVEST AS?

GAASSAND HOLDING AS is the largest registered owner, with 75.0%.

What is the revenue of OS INVEST AS?

OS INVEST AS had revenue of NOK 1.3m in 2025.

Where is OS INVEST AS based?

OS INVEST AS has its business address in Søfteland.

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.