BIZTRAC BETA
General cleaning of buildings

RENSOM GISKE AS

Org. no. 980129888 Limited company (AS) Giske Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 3.1m
Operating profit NOK 144,000
Equity NOK 183,000
Incorporated 1998
Employees 8
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RENSOM GISKE AS is registered as a limited company in Giske, Møre og Romsdal with organisation number 980129888. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 1998 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Handel, service og produksjon og det som hermed står i forbindelse, herunder å delta i andre selskap med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.1m in revenue and NOK 144,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.1m
Operating profit
NOK 144,000
Equity
NOK 183,000
Est. value
NOK 700,000

Financial health · 2024

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

Who owns RENSOM GISKE AS?

KAROLINE B AS
RENSOM GISKE AS
NOK 3.1m rev. · NOK 144,000 profit

RENSOM GISKE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

RENSOM GISKE AS er morselskap for 13 datterselskaper:

Frequently asked questions about RENSOM GISKE AS

Who owns RENSOM GISKE AS?

KAROLINE B AS is the largest registered owner, with 100.0%.

What is the revenue of RENSOM GISKE AS?

RENSOM GISKE AS had revenue of NOK 3.1m in 2024.

Where is RENSOM GISKE AS based?

RENSOM GISKE AS has its business address in Vigra.

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.