BIZTRAC BETA
Repair and maintenance of motor vehicles

TANA BILGLASS AS

Org. no. 986819274 Limited company (AS) Tana Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 15.9m
Operating profit NOK −46,000
Equity NOK 163,000
Incorporated 2004
Employees 13
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−46k kr).

TANA BILGLASS AS is registered as a limited company in Tana, Finnmark with organisation number 986819274. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2004 and has 13 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg og reparasjoner av scooter, sykler, frontruter og andre motorkjøretøy og dertil tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.9m in revenue and NOK −46,000 in operating profit.

Key figures · 2024

Revenue
NOK 15.9m
Operating profit
NOK −46,000
Equity
NOK 163,000
Est. value
NOK 7.8m

Financial health · 2024

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

Who owns TANA BILGLASS AS?

VEGARD BLIEN
TANA BILGLASS AS
NOK 15.9m rev. · NOK −46,000 profit

TANA BILGLASS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TANA BILGLASS AS

Who owns TANA BILGLASS AS?

VEGARD BLIEN is the largest registered owner, with 34.0%.

What is the revenue of TANA BILGLASS AS?

TANA BILGLASS AS had revenue of NOK 15.9m in 2024.

Who is the general manager of TANA BILGLASS AS?

Vegard Blien is registered as general manager of TANA BILGLASS AS.

Where is TANA BILGLASS AS based?

TANA BILGLASS AS has its business address in Tana.

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.