BIZTRAC BETA
Other health services

GLOW ESTHETICS AS

Org. no. 935234670 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 156,000
Operating profit NOK 2,000
Equity NOK 13,000
Incorporated 2025
Share capital NOK 30,000

GLOW ESTHETICS AS is registered as a limited company in Trondheim, Trøndelag with organisation number 935234670. The business is classified under other health services (NACE 86.993). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Estetisk medisin og relaterte tjenester, samt salg av tilknyttede produkter.”. The most recent filed accounts, for the 2025 financial year, show NOK 156,000 in revenue and NOK 2,000 in operating profit.

Key figures · 2025

Revenue
NOK 156,000
Operating profit
NOK 2,000
Equity
NOK 13,000
Est. value
NOK 15,000

Financial health · 2025

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

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

Who owns GLOW ESTHETICS AS?

MARØY ØSTENSEN HOLDING AS
GLOW ESTHETICS AS
NOK 156,000 rev. · NOK 2,000 profit

GLOW ESTHETICS AS has 1 registered shareholder:

All shareholders and roles →

Group structure

GLOW ESTHETICS AS er morselskap for 1 datterselskap:

Frequently asked questions about GLOW ESTHETICS AS

Who owns GLOW ESTHETICS AS?

MARØY ØSTENSEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GLOW ESTHETICS AS?

GLOW ESTHETICS AS had revenue of NOK 156,000 in 2025.

Who is the general manager of GLOW ESTHETICS AS?

Geir-Inge Marøy Østensen is registered as general manager of GLOW ESTHETICS AS.

Where is GLOW ESTHETICS AS based?

GLOW ESTHETICS AS has its business address in Heimdal.

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.