BIZTRAC BETA
Floor and wall covering

GULVSYSTEMER AS

Org. no. 958306415 Limited company (AS) Hamar Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 6.1m
Operating profit NOK −52,000
Equity NOK 170,000
Incorporated 1990
Employees 5
Share capital NOK 100,000

Signals

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

GULVSYSTEMER AS is registered as a limited company in Hamar, Innlandet with organisation number 958306415. The business is classified under floor and wall covering (NACE 43.330). The company was incorporated in 1990 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handel og tjenesteyting innenfor bygg- og anleggs- bransjen, samt hva hermed står i forbindelse, her- under å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.1m in revenue and NOK −52,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.1m
Operating profit
NOK −52,000
Equity
NOK 170,000
Est. value
NOK 2.2m

Financial health · 2025

Liquidity
1.08
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.0%
Satisfactory
Equity as a share of total capital

Who owns GULVSYSTEMER AS?

ØYSTEIN BAKKEHAUG
GULVSYSTEMER AS
NOK 6.1m rev. · NOK −52,000 profit

GULVSYSTEMER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULVSYSTEMER AS

Who owns GULVSYSTEMER AS?

ØYSTEIN BAKKEHAUG is the largest registered owner, with 100.0%.

What is the revenue of GULVSYSTEMER AS?

GULVSYSTEMER AS had revenue of NOK 6.1m in 2025.

Who is the general manager of GULVSYSTEMER AS?

Øystein Bakkehaug is registered as general manager of GULVSYSTEMER AS.

Where is GULVSYSTEMER AS based?

GULVSYSTEMER AS has its business address in Ridabu.

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.