BIZTRAC BETA
Graphic design and visual communication activities

BLUEROOM AS

Org. no. 880110322 Limited company (AS) Oslo Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 877,000
Operating profit NOK 216,000
Equity NOK 1.8m
Incorporated 1998
Share capital NOK 100,000

BLUEROOM AS is registered as a limited company in Oslo, Oslo with organisation number 880110322. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 1998. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Yte rådgivining og andre tjenester i forbindelse med utvikling av grafisk design, kommunikasjon og annen virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 877,000 in revenue and NOK 216,000 in operating profit.

Key figures · 2024

Revenue
NOK 877,000
Operating profit
NOK 216,000
Equity
NOK 1.8m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns BLUEROOM AS?

LINE RENEE HAGEN
BLUEROOM AS
NOK 877,000 rev. · NOK 216,000 profit

BLUEROOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BLUEROOM AS own?

BLUEROOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BLUEROOM AS

Who owns BLUEROOM AS?

LINE RENEE HAGEN is the largest registered owner, with 100.0%.

What is the revenue of BLUEROOM AS?

BLUEROOM AS had revenue of NOK 877,000 in 2024.

Who is the general manager of BLUEROOM AS?

Line Renee Hagen is registered as general manager of BLUEROOM AS.

Where is BLUEROOM AS based?

BLUEROOM AS has its business address in Oslo.

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.