BIZTRAC BETA
Research and experimental development on natural sciences and engineering

FOSS AS

Org. no. 997805925 Limited company (AS) Drammen Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 261,000
Equity NOK −717,000
Incorporated 2012
Share capital NOK 30,000

Signals

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

FOSS AS is registered as a limited company in Drammen, Buskerud with organisation number 997805925. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Teknologi- og konseptutvikling, konsulentvirksomhet, kjøp og salg av aksjer i andre selskaper, samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 261,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 261,000
Equity
NOK −717,000
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
0.28
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-101.9%
Weak
Equity as a share of total capital

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

Who owns FOSS AS?

STEIN FOSS
FOSS AS
NOK 1.0m rev. · NOK 261,000 profit

FOSS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FOSS AS own?

FOSS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FOSS AS

Who owns FOSS AS?

STEIN FOSS is the largest registered owner, with 100.0%.

What is the revenue of FOSS AS?

FOSS AS had revenue of NOK 1.0m in 2025.

Where is FOSS AS based?

FOSS AS has its business address in Drammen.

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.