BIZTRAC BETA
Landscape service activities

TJUGUM AS

Org. no. 916671288 Limited company (AS) Drammen Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 5.1m
Operating profit NOK 225,000
Equity NOK 649,000
Incorporated 2016
Share capital NOK 60,000

TJUGUM AS is registered as a limited company in Drammen, Buskerud with organisation number 916671288. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2016. Registered share capital is NOK 60,000, divided into 600 shares. The company's stated purpose is: “Gartner, anleggsgartnerarbeid samt utvendig/innvendig malearbeid og andre produkter/tjenester som naturlig hører til 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. Selskapet kan også drive med kjøp/salg/drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.1m in revenue and NOK 225,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.1m
Operating profit
NOK 225,000
Equity
NOK 649,000
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns TJUGUM AS?

OLE ANDRE KRISTIANSEN TJUGUM
TJUGUM AS
NOK 5.1m rev. · NOK 225,000 profit

TJUGUM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TJUGUM AS

Who owns TJUGUM AS?

OLE ANDRE KRISTIANSEN TJUGUM is the largest registered owner, with 50.0%.

What is the revenue of TJUGUM AS?

TJUGUM AS had revenue of NOK 5.1m in 2025.

Who is the general manager of TJUGUM AS?

Eivind Tjugum is registered as general manager of TJUGUM AS.

Where is TJUGUM AS based?

TJUGUM AS has its business address in Mjøndalen.

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.