BIZTRAC BETA
Roofing activities

ZELINA AS

Org. no. 926678604 Limited company (AS) Tromsø Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 100,000
Operating profit NOK 34,000
Equity NOK 3.7m
Incorporated 2021
Share capital NOK 360,000

ZELINA AS is registered as a limited company in Tromsø, Troms with organisation number 926678604. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2021. Registered share capital is NOK 360,000, divided into 600 shares. The company's stated purpose is: “Å drive med salg av varer og tjenester innenfor bygge og anleggsvirksomhet. Selskapets formål er også gjennom aksjer eller på annen måte å delta i virksomhet og selskaper med økonomiske formål, og alt som for øvrig står i forbindelse med dette. Videre skal også selskapet bistå med finansiering av andre selskap i konsern, herunder for eksempel yte lån.”. The most recent filed accounts, for the 2024 financial year, show NOK 100,000 in revenue and NOK 34,000 in operating profit.

Key figures · 2024

Revenue
NOK 100,000
Operating profit
NOK 34,000
Equity
NOK 3.7m
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns ZELINA AS?

STENULF MIKKELSEN
ZELINA AS
NOK 100,000 rev. · NOK 34,000 profit

ZELINA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ZELINA AS own?

ZELINA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ZELINA AS

Who owns ZELINA AS?

STENULF MIKKELSEN is the largest registered owner, with 100.0%.

What is the revenue of ZELINA AS?

ZELINA AS had revenue of NOK 100,000 in 2024.

Where is ZELINA AS based?

ZELINA 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.