BIZTRAC BETA
General cleaning of buildings

FINSTAD RENHOLD AS

Org. no. 911547147 Limited company (AS) Lørenskog Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 8.7m
Operating profit NOK 249,000
Equity NOK −431,000
Incorporated 2013
Employees 16
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−431k kr).

FINSTAD RENHOLD AS is registered as a limited company in Lørenskog, Akershus with organisation number 911547147. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2013 and has 16 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Renhold av næringslokaler.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.7m in revenue and NOK 249,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.7m
Operating profit
NOK 249,000
Equity
NOK −431,000
Est. value
NOK 2.1m

Financial health · 2025

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

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

Who owns FINSTAD RENHOLD AS?

SHERAFEDIN ISMAJLI
FINSTAD RENHOLD AS
NOK 8.7m rev. · NOK 249,000 profit

FINSTAD RENHOLD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FINSTAD RENHOLD AS

Who owns FINSTAD RENHOLD AS?

SHERAFEDIN ISMAJLI is the largest registered owner, with 50.0%.

What is the revenue of FINSTAD RENHOLD AS?

FINSTAD RENHOLD AS had revenue of NOK 8.7m in 2025.

Who is the general manager of FINSTAD RENHOLD AS?

Sherafedin Ismajli is registered as general manager of FINSTAD RENHOLD AS.

Where is FINSTAD RENHOLD AS based?

FINSTAD RENHOLD AS has its business address in Finstadjordet.

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.