BIZTRAC BETA
General cleaning of buildings

EK RENGJØRING OG VEDLIKEHOLD AS

Org. no. 927198215 Limited company (AS) Halden Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 892,000
Operating profit NOK 5,000
Equity NOK 122,000
Incorporated 2021
Share capital NOK 80,000

EK RENGJØRING OG VEDLIKEHOLD AS is registered as a limited company in Halden, Østfold with organisation number 927198215. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2021. Registered share capital is NOK 80,000, divided into 1000 shares. The company's stated purpose is: “Rengjøringstjenester, vaktmestertjenester, vedlikehold og flyttetjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 892,000 in revenue and NOK 5,000 in operating profit.

Key figures · 2025

Revenue
NOK 892,000
Operating profit
NOK 5,000
Equity
NOK 122,000
Est. value
NOK 85,000

Financial health · 2025

Liquidity
1.65
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
41.5%
Very good
Equity as a share of total capital

Who owns EK RENGJØRING OG VEDLIKEHOLD AS?

LINDITA KUQI
EK RENGJØRING OG VEDLIKEHOLD AS
NOK 892,000 rev. · NOK 5,000 profit

EK RENGJØRING OG VEDLIKEHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EK RENGJØRING OG VEDLIKEHOLD AS

Who owns EK RENGJØRING OG VEDLIKEHOLD AS?

LINDITA KUQI is the largest registered owner, with 100.0%.

What is the revenue of EK RENGJØRING OG VEDLIKEHOLD AS?

EK RENGJØRING OG VEDLIKEHOLD AS had revenue of NOK 892,000 in 2025.

Who is the general manager of EK RENGJØRING OG VEDLIKEHOLD AS?

Lindita Kuqi is registered as general manager of EK RENGJØRING OG VEDLIKEHOLD AS.

Where is EK RENGJØRING OG VEDLIKEHOLD AS based?

EK RENGJØRING OG VEDLIKEHOLD AS has its business address in Halden.

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.