BIZTRAC BETA
COMPANY REGISTER PROFILE
976118553 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Production of meat and poultry meat products

SPEKELOFTET AS

Org. no. 976118553 Limited company (AS) Hemsedal Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 111.7m
Operating profit NOK 14.6m
Equity NOK 6.1m
Incorporated 1996
Employees 9
Share capital NOK 142,000

SPEKELOFTET AS is registered as a limited company in Hemsedal, Buskerud with organisation number 976118553. The business is classified under production of meat and poultry meat products (NACE 10.130). The company was incorporated in 1996 and has 9 registered employees. Registered share capital is NOK 142,000, divided into 300 shares. The company's stated purpose is: “Produksjon, kjøp og salg av kjøtt- og fiskeprodukter, investering i andre selskaper og eiendom samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 111.7m in revenue and NOK 14.6m in operating profit.

Key figures · 2025

Revenue
NOK 111.7m
▲ +1 %
Operating profit
NOK 14.6m
▲ +15 %
Equity
NOK 6.1m
▲ +17 %
Est. value
NOK 54.3m

Financial health · 2025

Liquidity
1.12
Satisfactory
Current assets ÷ current liabilities
Profitability
45.5%
Very good
Return on total assets
Solidity
17.0%
Satisfactory
Equity as a share of total capital

Who owns SPEKELOFTET AS?

SPEKELOFTET AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SPEKELOFTET AS

Who owns SPEKELOFTET AS?

REMA INDUSTRIER AS is the largest registered owner, with 50.0%.

What is the revenue of SPEKELOFTET AS?

SPEKELOFTET AS had revenue of NOK 111.7m in 2025.

Who is the general manager of SPEKELOFTET AS?

Ole Halvard Venås is registered as general manager of SPEKELOFTET AS.

Where is SPEKELOFTET AS based?

SPEKELOFTET AS has its business address in Hemsedal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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