BIZTRAC BETA
General cleaning of buildings

ULLENSAKER RENHOLDSTEKNIKK AS

Org. no. 995939258 Limited company (AS) Ullensaker Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 17.4m
Operating profit NOK 644,000
Equity NOK 2.0m
Incorporated 2010
Employees 38
Share capital NOK 100,000

ULLENSAKER RENHOLDSTEKNIKK AS is registered as a limited company in Ullensaker, Akershus with organisation number 995939258. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2010 and has 38 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Rengjøring samt annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.4m in revenue and NOK 644,000 in operating profit.

Key figures · 2024

Revenue
NOK 17.4m
Operating profit
NOK 644,000
Equity
NOK 2.0m
Est. value
NOK 3.5m

Financial health · 2024

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

Who owns ULLENSAKER RENHOLDSTEKNIKK AS?

AGIM THAQI
ULLENSAKER RENHOLDSTEKNIKK AS
NOK 17.4m rev. · NOK 644,000 profit

ULLENSAKER RENHOLDSTEKNIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ULLENSAKER RENHOLDSTEKNIKK AS

Who owns ULLENSAKER RENHOLDSTEKNIKK AS?

AGIM THAQI is the largest registered owner, with 70.0%.

What is the revenue of ULLENSAKER RENHOLDSTEKNIKK AS?

ULLENSAKER RENHOLDSTEKNIKK AS had revenue of NOK 17.4m in 2024.

Who is the general manager of ULLENSAKER RENHOLDSTEKNIKK AS?

Agim Thaqi is registered as general manager of ULLENSAKER RENHOLDSTEKNIKK AS.

Where is ULLENSAKER RENHOLDSTEKNIKK AS based?

ULLENSAKER RENHOLDSTEKNIKK AS has its business address in Kløfta.

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.