BIZTRAC BETA
Rental and operating of own or leased real estate

TRANGO I AS

Org. no. 988120928 Limited company (AS) Bærum Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −35,000
Equity NOK 25.1m
Incorporated 2005
Share capital NOK 100,000

Signals

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

TRANGO I AS is registered as a limited company in Bærum, Akershus with organisation number 988120928. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investere i aksjer, eiendom og hester og virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −35,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −35,000
Equity
NOK 25.1m
Est. value
NOK 20.4m

Financial health · 2025

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

Who owns TRANGO I AS?

STEN-ARTHUR SÆLØR
TRANGO I AS
NOK 0 rev. · NOK −35,000 profit

TRANGO I AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TRANGO I AS own?

TRANGO I AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TRANGO I AS

Who owns TRANGO I AS?

STEN-ARTHUR SÆLØR is the largest registered owner, with 100.0%.

What is the revenue of TRANGO I AS?

TRANGO I AS had revenue of NOK 0 in 2025.

Who is the general manager of TRANGO I AS?

Sten-Arthur Sælør is registered as general manager of TRANGO I AS.

Where is TRANGO I AS based?

TRANGO I AS has its business address in Østerås.

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.