BIZTRAC BETA
General cleaning of buildings

TORBEN W RASMUSSEN AS

Org. no. 979519478 Limited company (AS) Tinn Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 7.1m
Operating profit NOK 194,000
Equity NOK 2.6m
Incorporated 1997
Employees 21
Share capital NOK 600,000

TORBEN W RASMUSSEN AS is registered as a limited company in Tinn, Telemark with organisation number 979519478. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 1997 and has 21 registered employees. Registered share capital is NOK 600,000, divided into 600 shares. The company's stated purpose is: “Drive rengjøring og flislegging samt annen virksomhet som står i forbindelse med disse næringsområder. Selskapet kan også engasjere seg i andre virksomhetsområder.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.1m in revenue and NOK 194,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.1m
Operating profit
NOK 194,000
Equity
NOK 2.6m
Est. value
NOK 2.3m

Financial health · 2024

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

Who owns TORBEN W RASMUSSEN AS?

WESTBERG AS
TORBEN W RASMUSSEN AS
NOK 7.1m rev. · NOK 194,000 profit

TORBEN W RASMUSSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TORBEN W RASMUSSEN AS

Who owns TORBEN W RASMUSSEN AS?

WESTBERG AS is the largest registered owner, with 100.0%.

What is the revenue of TORBEN W RASMUSSEN AS?

TORBEN W RASMUSSEN AS had revenue of NOK 7.1m in 2024.

Who is the general manager of TORBEN W RASMUSSEN AS?

Johannes Westberg Rasmussen is registered as general manager of TORBEN W RASMUSSEN AS.

Where is TORBEN W RASMUSSEN AS based?

TORBEN W RASMUSSEN AS has its business address in Rjukan.

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.