BIZTRAC BETA
General cleaning of buildings

FRAM RENHOLDERE AS

Org. no. 924555955 Limited company (AS) Kongsberg Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 58,000
Equity NOK −325,000
Incorporated 2020
Employees 10
Share capital NOK 30,000

Signals

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

FRAM RENHOLDERE AS is registered as a limited company in Kongsberg, Buskerud with organisation number 924555955. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2020 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Renholdsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 58,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 58,000
Equity
NOK −325,000
Est. value
NOK 316,000

Financial health · 2025

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

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

Who owns FRAM RENHOLDERE AS?

ANETTE PEDERSEN
FRAM RENHOLDERE AS
NOK 2.6m rev. · NOK 58,000 profit

FRAM RENHOLDERE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FRAM RENHOLDERE AS

Who owns FRAM RENHOLDERE AS?

ANETTE PEDERSEN is the largest registered owner, with 50.0%.

What is the revenue of FRAM RENHOLDERE AS?

FRAM RENHOLDERE AS had revenue of NOK 2.6m in 2025.

Who is the general manager of FRAM RENHOLDERE AS?

Egle Astrauske is registered as general manager of FRAM RENHOLDERE AS.

Where is FRAM RENHOLDERE AS based?

FRAM RENHOLDERE AS has its business address in Kongsberg.

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.