BIZTRAC BETA
Landscape service activities

TRANBY AS

Org. no. 986358722 Limited company (AS) Bærum Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 50.5m
Operating profit NOK 3.5m
Equity NOK 6.8m
Incorporated 2003
Employees 27
Share capital NOK 1.4m

TRANBY AS is registered as a limited company in Bærum, Akershus with organisation number 986358722. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2003 and has 27 registered employees. Registered share capital is NOK 1.4m, divided into 1400 shares. The company's stated purpose is: “Entreprenør- og anleggsgartnervirksomhet, herunder også kjøp av planter. Selskapet kan ved kjøp og salg av aksjer engasjere seg i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 50.5m in revenue and NOK 3.5m in operating profit.

Key figures · 2025

Revenue
NOK 50.5m
Operating profit
NOK 3.5m
Equity
NOK 6.8m
Est. value
NOK 18.3m

Financial health · 2025

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

Who owns TRANBY AS?

JANTY INVEST AS
TRANBY AS
NOK 50.5m rev. · NOK 3.5m profit

TRANBY AS has 8 registered shareholders:

All shareholders and roles →

Which companies does TRANBY AS own?

TRANBY AS holds a stake in 1 company:

See the full ownership structure →

Group structure

TRANBY AS er morselskap for 1 datterselskap:

Frequently asked questions about TRANBY AS

Who owns TRANBY AS?

JANTY INVEST AS is the largest registered owner, with 90.1%.

What is the revenue of TRANBY AS?

TRANBY AS had revenue of NOK 50.5m in 2025.

Who is the general manager of TRANBY AS?

Adrian Rossvoll Tranby is registered as general manager of TRANBY AS.

Where is TRANBY AS based?

TRANBY AS has its business address in Vøyenenga.

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.