BIZTRAC BETA
Joinery installation

ROYAL HOUSE AS

Org. no. 925211850 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 63,000
Equity NOK −781,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−781k kr).

ROYAL HOUSE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 925211850. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Snekring og montering, samt kjøp, oppussing og utleie av hus, og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 63,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 63,000
Equity
NOK −781,000
Est. value
NOK 280,000

Financial health · 2025

Liquidity
2.44
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-13.4%
Weak
Equity as a share of total capital

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

Who owns ROYAL HOUSE AS?

MICHAL CIECHANOWICZ
ROYAL HOUSE AS
NOK 2.0m rev. · NOK 63,000 profit

ROYAL HOUSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROYAL HOUSE AS

Who owns ROYAL HOUSE AS?

MICHAL CIECHANOWICZ is the largest registered owner, with 100.0%.

What is the revenue of ROYAL HOUSE AS?

ROYAL HOUSE AS had revenue of NOK 2.0m in 2025.

Who is the general manager of ROYAL HOUSE AS?

Michal Ciechanowicz is registered as general manager of ROYAL HOUSE AS.

Where is ROYAL HOUSE AS based?

ROYAL HOUSE AS has its business address in Sjetnemarka.

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.