BIZTRAC BETA
Landscape service activities

SQUAREROOT AS

Org. no. 926664972 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 25,000
Incorporated 2021
Share capital NOK 32,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).

SQUAREROOT AS is registered as a limited company in Oslo, Oslo with organisation number 926664972. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2021. Registered share capital is NOK 32,000, divided into 32190 shares. The company's stated purpose is: “Utvikling, kommersialisering, installasjon av grønne arealer i byer og bygninger og annet som naturlig faller sammen med dette kan bli en del av selskapets virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 25,000
Est. value
NOK 37,000

Financial health · 2025

Liquidity
1.89
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
47.2%
Weak
Equity as a share of total capital

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

Who owns SQUAREROOT AS?

ADVENGE CONSULTING AS
SQUAREROOT AS
NOK 0 rev. · NOK −10,000 profit

SQUAREROOT AS has 10 registered shareholders:

All shareholders and roles →

Frequently asked questions about SQUAREROOT AS

Who owns SQUAREROOT AS?

ADVENGE CONSULTING AS is the largest registered owner, with 93.2%.

What is the revenue of SQUAREROOT AS?

SQUAREROOT AS had revenue of NOK 0 in 2025.

Who is the general manager of SQUAREROOT AS?

Michel Joseph Maurice Wolfstirn is registered as general manager of SQUAREROOT AS.

Where is SQUAREROOT AS based?

SQUAREROOT 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.