BIZTRAC BETA
Graphic design and visual communication activities

GROWLAB OSLO AS

Org. no. 915133479 Limited company (AS) Molde Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 127,000
Equity NOK 170,000
Incorporated 2015
Share capital NOK 30,000

GROWLAB OSLO AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 915133479. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av designtjenester i form av visuell kommunikasjon, interiørarkitektur og produktdesign og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 127,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 127,000
Equity
NOK 170,000
Est. value
NOK 736,000

Financial health · 2025

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

Who owns GROWLAB OSLO AS?

TABEA JURINE GLAHS
GROWLAB OSLO AS
NOK 1.0m rev. · NOK 127,000 profit

GROWLAB OSLO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GROWLAB OSLO AS

Who owns GROWLAB OSLO AS?

TABEA JURINE GLAHS is the largest registered owner, with 50.0%.

What is the revenue of GROWLAB OSLO AS?

GROWLAB OSLO AS had revenue of NOK 1.0m in 2025.

Who is the general manager of GROWLAB OSLO AS?

Mads Hårstad Pålsrud is registered as general manager of GROWLAB OSLO AS.

Where is GROWLAB OSLO AS based?

GROWLAB OSLO AS has its business address in Molde.

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.