BIZTRAC BETA
Manufacture of other food products n.e.c.

SAGAMAT AS

Org. no. 979699840 Limited company (AS) Steinkjer Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 8.1m
Operating profit NOK 405,000
Equity NOK 5.0m
Incorporated 1998
Employees 5
Share capital NOK 610,000

SAGAMAT AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 979699840. The business is classified under manufacture of other food products n.e.c. (NACE 10.890). The company was incorporated in 1998 and has 5 registered employees. Registered share capital is NOK 610,000, divided into 610 shares. The company's stated purpose is: “Produksjon/foredling og salg av produkter i hovedsak basert på råvarer fra naturen, samt virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.1m in revenue and NOK 405,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.1m
Operating profit
NOK 405,000
Equity
NOK 5.0m
Est. value
NOK 4.8m

Financial health · 2024

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

Who owns SAGAMAT AS?

ARVID OLA HATLING
SAGAMAT AS
NOK 8.1m rev. · NOK 405,000 profit

SAGAMAT AS has 9 registered shareholders:

All shareholders and roles →

Which companies does SAGAMAT AS own?

SAGAMAT AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SAGAMAT AS

Who owns SAGAMAT AS?

ARVID OLA HATLING is the largest registered owner, with 30.0%.

What is the revenue of SAGAMAT AS?

SAGAMAT AS had revenue of NOK 8.1m in 2024.

Who is the general manager of SAGAMAT AS?

Lasse Guldvik is registered as general manager of SAGAMAT AS.

Where is SAGAMAT AS based?

SAGAMAT AS has its business address in Steinkjer.

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.