BIZTRAC BETA
General cleaning of buildings

EKOGEN RENHOLD AS

Org. no. 831424532 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 413,000
Equity NOK 510,000
Incorporated 2023
Employees 8
Share capital NOK 30,000

EKOGEN RENHOLD AS is registered as a limited company in Bergen, Vestland with organisation number 831424532. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2023 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Levering alle typer renholdløsninger. Temporært renhold, vindusvask, privat renhold, kantinedrift.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 413,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 413,000
Equity
NOK 510,000
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
0.88
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.2%
Good
Equity as a share of total capital

Who owns EKOGEN RENHOLD AS?

KONUL GULIYEVA
EKOGEN RENHOLD AS
NOK 3.5m rev. · NOK 413,000 profit

EKOGEN RENHOLD AS has 2 registered shareholders:

All shareholders and roles →

Which companies does EKOGEN RENHOLD AS own?

EKOGEN RENHOLD AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EKOGEN RENHOLD AS

Who owns EKOGEN RENHOLD AS?

KONUL GULIYEVA is the largest registered owner, with 50.0%.

What is the revenue of EKOGEN RENHOLD AS?

EKOGEN RENHOLD AS had revenue of NOK 3.5m in 2025.

Who is the general manager of EKOGEN RENHOLD AS?

Mehmet Mahmood is registered as general manager of EKOGEN RENHOLD AS.

Where is EKOGEN RENHOLD AS based?

EKOGEN RENHOLD AS has its business address in Bergen.

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.