BIZTRAC BETA
Other building and industrial cleaning activities

ULTRA RENHOLD AS

Org. no. 935153158 Limited company (AS) Lillestrøm Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 283,000
Equity NOK 250,000
Incorporated 2025
Employees 17
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-02-27 Adresseendring registrert 2026-02-27.

ULTRA RENHOLD AS is registered as a limited company in Lillestrøm, Akershus with organisation number 935153158. The business is classified under other building and industrial cleaning activities (NACE 81.220). The company was incorporated in 2025 and has 17 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Renholdsvirksomhet og vaktmestertjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 283,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 283,000
Equity
NOK 250,000
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns ULTRA RENHOLD AS?

JUAN CARLOS RECABARREN GOMEZ
ULTRA RENHOLD AS
NOK 2.8m rev. · NOK 283,000 profit

ULTRA RENHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ULTRA RENHOLD AS

Who owns ULTRA RENHOLD AS?

JUAN CARLOS RECABARREN GOMEZ is the largest registered owner, with 100.0%.

What is the revenue of ULTRA RENHOLD AS?

ULTRA RENHOLD AS had revenue of NOK 2.8m in 2025.

Who is the general manager of ULTRA RENHOLD AS?

Juan Carlos Recabarren Gomez is registered as general manager of ULTRA RENHOLD AS.

Where is ULTRA RENHOLD AS based?

ULTRA RENHOLD AS has its business address in Skedsmokorset.

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.