BIZTRAC BETA
Rental and operating of own or leased real estate

TBE SKATTØRVEGEN 50 AS

Org. no. 895584592 Limited company (AS) Tromsø Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK 1.5m
Equity NOK 4.5m
Incorporated 2010
Share capital NOK 380,000

Signals

1 flags
  • Nylig endring 2026-03-12 Adresseendring registrert 2026-03-12.

TBE SKATTØRVEGEN 50 AS is registered as a limited company in Tromsø, Troms with organisation number 895584592. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 380,000, divided into 380000 shares. The company's stated purpose is: “Kjøpe, selge, utvikle, bygge ut, drifte, leie ut og på annen måte forvalte fast eiendom samt alt som naturlig står i forbindelse med det ovennevnte. Selskapet kan delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK 1.5m
Equity
NOK 4.5m
Est. value
NOK 5.5m

Financial health · 2024

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

Who owns TBE SKATTØRVEGEN 50 AS?

TEKNISK BUREAU ENGROS AS
TBE SKATTØRVEGEN 50 AS
NOK 2.3m rev. · NOK 1.5m profit

TBE SKATTØRVEGEN 50 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TBE SKATTØRVEGEN 50 AS

Who owns TBE SKATTØRVEGEN 50 AS?

TEKNISK BUREAU ENGROS AS is the largest registered owner, with 100.0%.

What is the revenue of TBE SKATTØRVEGEN 50 AS?

TBE SKATTØRVEGEN 50 AS had revenue of NOK 2.3m in 2024.

Where is TBE SKATTØRVEGEN 50 AS based?

TBE SKATTØRVEGEN 50 AS has its business address in Tromsø.

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.