BIZTRAC BETA
Retail sale of meat and meat products

SKIEN KJØTTFORRETNING AS

Org. no. 928471977 Limited company (AS) Skien Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 6.3m
Operating profit NOK 88,000
Equity NOK 25,000
Incorporated 2021
Share capital NOK 30,000

SKIEN KJØTTFORRETNING AS is registered as a limited company in Skien, Telemark with organisation number 928471977. The business is classified under retail sale of meat and meat products (NACE 47.220). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøpe og selge kjøtt og for øvrig drive med det som naturlig følger av dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.3m in revenue and NOK 88,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.3m
Operating profit
NOK 88,000
Equity
NOK 25,000
Est. value
NOK 329,000

Financial health · 2025

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SKIEN KJØTTFORRETNING AS?

ELIAS ADAM ALAWAD
SKIEN KJØTTFORRETNING AS
NOK 6.3m rev. · NOK 88,000 profit

SKIEN KJØTTFORRETNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKIEN KJØTTFORRETNING AS

Who owns SKIEN KJØTTFORRETNING AS?

ELIAS ADAM ALAWAD is the largest registered owner, with 100.0%.

What is the revenue of SKIEN KJØTTFORRETNING AS?

SKIEN KJØTTFORRETNING AS had revenue of NOK 6.3m in 2025.

Who is the general manager of SKIEN KJØTTFORRETNING AS?

Elias Adam Alawad is registered as general manager of SKIEN KJØTTFORRETNING AS.

Where is SKIEN KJØTTFORRETNING AS based?

SKIEN KJØTTFORRETNING AS has its business address in Skien.

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.