BIZTRAC BETA
Landscape service activities

TAG UTLEIE AS

Org. no. 916924208 Limited company (AS) Trondheim Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 56,000
Operating profit NOK −5,000
Equity NOK 46,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

TAG UTLEIE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 916924208. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Anleggsgartnervirksomhet, utleie av driftsmidler og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 56,000 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 56,000
Operating profit
NOK −5,000
Equity
NOK 46,000
Est. value
NOK 44,000

Financial health · 2025

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

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

Who owns TAG UTLEIE AS?

ARNE ANDREAS GRENDSTAD
TAG UTLEIE AS
NOK 56,000 rev. · NOK −5,000 profit

TAG UTLEIE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TAG UTLEIE AS

Who owns TAG UTLEIE AS?

ARNE ANDREAS GRENDSTAD is the largest registered owner, with 50.0%.

What is the revenue of TAG UTLEIE AS?

TAG UTLEIE AS had revenue of NOK 56,000 in 2025.

Where is TAG UTLEIE AS based?

TAG UTLEIE AS has its business address in Klæbu.

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.