BIZTRAC BETA
General cleaning of buildings

EKSTRA RENHOLD AS

Org. no. 931712454 Limited company (AS) Aurskog-Høland Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 597,000
Operating profit NOK −127,000
Equity NOK −107,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−107k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−127k kr).

EKSTRA RENHOLD AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 931712454. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Renhold.”. The most recent filed accounts, for the 2025 financial year, show NOK 597,000 in revenue and NOK −127,000 in operating profit.

Key figures · 2025

Revenue
NOK 597,000
Operating profit
NOK −127,000
Equity
NOK −107,000

Financial health · 2025

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-204.1%
Weak
Equity as a share of total capital

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

Who owns EKSTRA RENHOLD AS?

Viktorija Zyliene
EKSTRA RENHOLD AS
NOK 597,000 rev. · NOK −127,000 profit

EKSTRA RENHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EKSTRA RENHOLD AS

Who owns EKSTRA RENHOLD AS?

Viktorija Zyliene is the largest registered owner, with 100.0%.

What is the revenue of EKSTRA RENHOLD AS?

EKSTRA RENHOLD AS had revenue of NOK 597,000 in 2025.

Who is the general manager of EKSTRA RENHOLD AS?

Viktorija Zyliene is registered as general manager of EKSTRA RENHOLD AS.

Where is EKSTRA RENHOLD AS based?

EKSTRA RENHOLD AS has its business address in Setskog.

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.