BIZTRAC BETA
Sewerage

FOSS HØYTRYKK AS

Org. no. 932488493 Limited company (AS) Nesodden Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 134,000
Equity NOK 39,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-03-09 Adresseendring registrert 2026-03-09.

FOSS HØYTRYKK AS is registered as a limited company in Nesodden, Akershus with organisation number 932488493. The business is classified under sewerage (NACE 37.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Spyle- og sugebiltjenester, samt alt som naturlig hører hjemme under rørinspeksjon, sanering av tanker og industritjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 134,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 134,000
Equity
NOK 39,000
Est. value
NOK 336,000

Financial health · 2024

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

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

Who owns FOSS HØYTRYKK AS?

GEIR ROLF GUSTAVSEN
FOSS HØYTRYKK AS
NOK 2.1m rev. · NOK 134,000 profit

FOSS HØYTRYKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOSS HØYTRYKK AS

Who owns FOSS HØYTRYKK AS?

GEIR ROLF GUSTAVSEN is the largest registered owner, with 100.0%.

What is the revenue of FOSS HØYTRYKK AS?

FOSS HØYTRYKK AS had revenue of NOK 2.1m in 2024.

Who is the general manager of FOSS HØYTRYKK AS?

Geir Rolf Gustavsen is registered as general manager of FOSS HØYTRYKK AS.

Where is FOSS HØYTRYKK AS based?

FOSS HØYTRYKK AS has its business address in Bjørnemyr.

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.