BIZTRAC BETA
Retail sale of carpets, rugs, wall and floor coverings

GULVMAX AS

Org. no. 979549466 Limited company (AS) Stavanger Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 39.8m
Operating profit NOK 4.2m
Equity NOK 4.2m
Incorporated 1998
Employees 8
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GULVMAX AS is registered as a limited company in Stavanger, Rogaland with organisation number 979549466. The business is classified under retail sale of carpets, rugs, wall and floor coverings (NACE 47.530). The company was incorporated in 1998 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handel og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 39.8m in revenue and NOK 4.2m in operating profit.

Key figures · 2024

Revenue
NOK 39.8m
Operating profit
NOK 4.2m
Equity
NOK 4.2m
Est. value
NOK 15.2m

Financial health · 2024

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

Who owns GULVMAX AS?

IBO HOLDING AS
GULVMAX AS
NOK 39.8m rev. · NOK 4.2m profit

GULVMAX AS has 1 registered shareholder:

All shareholders and roles →

Group structure

GULVMAX AS er morselskap for 6 datterselskaper:

Frequently asked questions about GULVMAX AS

Who owns GULVMAX AS?

IBO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GULVMAX AS?

GULVMAX AS had revenue of NOK 39.8m in 2024.

Who is the general manager of GULVMAX AS?

Trond Pedersen is registered as general manager of GULVMAX AS.

Where is GULVMAX AS based?

GULVMAX AS has its business address in Stavanger.

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.