BIZTRAC BETA
Other content distribution activities

ROOMSKETCHER AS

Org. no. 991008683 Limited company (AS) Bærum Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 63.8m
Operating profit NOK 7.1m
Equity NOK 45.4m
Incorporated 2007
Employees 19
Share capital NOK 23.5m

Signals

1 flags
  • Nylig endring 2026-04-23 Aksjekapital registrert 2026-04-23.

ROOMSKETCHER AS is registered as a limited company in Bærum, Akershus with organisation number 991008683. The business is classified under other content distribution activities (NACE 60.390). The company was incorporated in 2007 and has 19 registered employees. Registered share capital is NOK 23.5m, divided into 147000000 shares. The company's stated purpose is: “Konsulentbistand og skreddersøm av løsninger innen 3D visualisering, animasjon, VR og generell anvendelse av multimedia og presentasjoner.”. The most recent filed accounts, for the 2025 financial year, show NOK 63.8m in revenue and NOK 7.1m in operating profit.

Key figures · 2025

Revenue
NOK 63.8m
Operating profit
NOK 7.1m
Equity
NOK 45.4m
Est. value
NOK 68.5m

Financial health · 2025

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

Who owns ROOMSKETCHER AS?

TORREY PINES AS
ROOMSKETCHER AS
NOK 63.8m rev. · NOK 7.1m profit

ROOMSKETCHER AS has 15 registered shareholders:

All shareholders and roles →

Frequently asked questions about ROOMSKETCHER AS

Who owns ROOMSKETCHER AS?

TORREY PINES AS is the largest registered owner, with 69.5%.

What is the revenue of ROOMSKETCHER AS?

ROOMSKETCHER AS had revenue of NOK 63.8m in 2025.

Who is the general manager of ROOMSKETCHER AS?

Trond Bergquist is registered as general manager of ROOMSKETCHER AS.

Where is ROOMSKETCHER AS based?

ROOMSKETCHER AS has its business address in Lysaker.

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.