BIZTRAC BETA
Floor and wall covering

ELEGANTE GULV AS

Org. no. 928105040 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2023 NOK 2.2m
Operating profit NOK −75,000
Equity NOK 224,000
Incorporated 2021
Share capital NOK 30,000

Signals

3 flags
  • Driftsunderskudd 2023 Siste driftsresultat er negativt (−75k kr).
  • Utdatert regnskap Siste registrerte regnskap er fra 2023.
  • Nylig endring 2026-06-11 Under avvikling registrert 2026-06-11.

ELEGANTE GULV AS is registered as a limited company in Oslo, Oslo with organisation number 928105040. The business is classified under floor and wall covering (NACE 43.330). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive med følgende tjenester: Gulvlegging, gulvsliping. Forebygging og fjerning av fuktproblemer i bygg. Generelle bygg- og oppussingtjenester.”. The most recent filed accounts, for the 2023 financial year, show NOK 2.2m in revenue and NOK −75,000 in operating profit.

Key figures · 2023

Revenue
NOK 2.2m
Operating profit
NOK −75,000
Equity
NOK 224,000
Est. value
NOK 850,000

Financial health · 2023

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
60.3%
Very good
Equity as a share of total capital

Who owns ELEGANTE GULV AS?

No shareholders are registered for ELEGANTE GULV AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ELEGANTE GULV AS

What is the revenue of ELEGANTE GULV AS?

ELEGANTE GULV AS had revenue of NOK 2.2m in 2023.

Who is the general manager of ELEGANTE GULV AS?

Rebaz Safa Shamal is registered as general manager of ELEGANTE GULV AS.

Where is ELEGANTE GULV AS based?

ELEGANTE GULV AS has its business address in Oslo.

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.