BIZTRAC BETA
Rental and operating of own or leased real estate

TANKE SVILANDSGATE 73 AS

Org. no. 987676183 Limited company (AS) Bærum Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 5.6m
Operating profit NOK 1.2m
Equity NOK 840,000
Incorporated 2004
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TANKE SVILANDSGATE 73 AS is registered as a limited company in Bærum, Akershus with organisation number 987676183. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og drive fast eiendom, samt å delta som akjsonær i andre selskaper og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.6m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 5.6m
Operating profit
NOK 1.2m
Equity
NOK 840,000
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns TANKE SVILANDSGATE 73 AS?

BACKE PROSJEKT AS
TANKE SVILANDSGATE 73 AS
NOK 5.6m rev. · NOK 1.2m profit

TANKE SVILANDSGATE 73 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANKE SVILANDSGATE 73 AS

Who owns TANKE SVILANDSGATE 73 AS?

BACKE PROSJEKT AS is the largest registered owner, with 100.0%.

What is the revenue of TANKE SVILANDSGATE 73 AS?

TANKE SVILANDSGATE 73 AS had revenue of NOK 5.6m in 2025.

Where is TANKE SVILANDSGATE 73 AS based?

TANKE SVILANDSGATE 73 AS has its business address in Lysaker.

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.