biztrac. BETA
COMPANY REGISTER PROFILE
984573308 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Manufacture of hollow glass

BLÅST AS

Org. no. 984573308 Limited company (AS) Tromsø Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 4.7m
Operating profit NOK 285,000
Equity NOK 1.4m
Incorporated 2002
Employees 12
Share capital NOK 200,000

BLÅST AS is registered as a limited company in Tromsø, Troms with organisation number 984573308. The business is classified under manufacture of hollow glass (NACE 23.130). The company was incorporated in 2002 and has 12 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Glassblåsing, produksjon og salg av egne håndlagde produkter, samt annen virksomhet som naturlig hører herunder.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.7m in revenue and NOK 285,000 in operating profit.

Former names: BLÅST GLASSHYTTA I TROMSØ AS

Key figures · 2025

Revenue
NOK 4.7m
▲ +3 %
Operating profit
NOK 285,000
▼ −23 %
Equity
NOK 1.4m
▲ +6 %
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
2.02
Very good
Current assets ÷ current liabilities
Profitability
9.2%
Satisfactory
Return on total assets
Solidity
43.2%
Very good
Equity as a share of total capital

Who owns BLÅST AS?

BLÅST AS has 3 registered shareholders:

All shareholders and roles →

Which companies does BLÅST AS own?

BLÅST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BLÅST AS

Who owns BLÅST AS?

BLÅST AS is the largest registered owner, with 50.0%.

What is the revenue of BLÅST AS?

BLÅST AS had revenue of NOK 4.7m in 2025.

Who is the general manager of BLÅST AS?

Silja Skoglund is registered as general manager of BLÅST AS.

Where is BLÅST AS based?

BLÅST 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.