BIZTRAC BETA
Finishing of textiles

RMZ COMPANY AS

Org. no. 925258571 Limited company (AS) Kongsberg Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK 11,000
Equity NOK −1.4m
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,4 mill kr).

RMZ COMPANY AS is registered as a limited company in Kongsberg, Buskerud with organisation number 925258571. The business is classified under finishing of textiles (NACE 13.300). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Profilering, trykk og brodering av klær. Butikk og netthandel, salg av produkter til hest og rytter. Rideundervisning.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK 11,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK 11,000
Equity
NOK −1.4m
Est. value
NOK 52,000

Financial health · 2024

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

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

Who owns RMZ COMPANY AS?

GLENN ANDRE THORESEN
RMZ COMPANY AS
NOK 1.0m rev. · NOK 11,000 profit

RMZ COMPANY AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RMZ COMPANY AS

Who owns RMZ COMPANY AS?

GLENN ANDRE THORESEN is the largest registered owner, with 50.0%.

What is the revenue of RMZ COMPANY AS?

RMZ COMPANY AS had revenue of NOK 1.0m in 2024.

Who is the general manager of RMZ COMPANY AS?

Silje Hammervold Kristiansen is registered as general manager of RMZ COMPANY AS.

Where is RMZ COMPANY AS based?

RMZ COMPANY AS has its business address in Skollenborg.

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.