BIZTRAC BETA
Technical testing and analysis

MATPULS AS

Org. no. 913246721 Limited company (AS) Lillehammer Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK −57,000
Equity NOK 91,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−57k kr).

MATPULS AS is registered as a limited company in Lillehammer, Innlandet with organisation number 913246721. The business is classified under technical testing and analysis (NACE 71.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Rådgiving og veiledning innen matsikkerhet, hygiene, internkontroll for alle bedrifter som driver produksjon og omsetning av næringsmidler, samt virksomhet som har naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK −57,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK −57,000
Equity
NOK 91,000
Est. value
NOK 1.3m

Financial health · 2025

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

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

Who owns MATPULS AS?

HEGE SKARI
MATPULS AS
NOK 1.2m rev. · NOK −57,000 profit

MATPULS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MATPULS AS

Who owns MATPULS AS?

HEGE SKARI is the largest registered owner, with 100.0%.

What is the revenue of MATPULS AS?

MATPULS AS had revenue of NOK 1.2m in 2025.

Who is the general manager of MATPULS AS?

Hege Skari is registered as general manager of MATPULS AS.

Where is MATPULS AS based?

MATPULS AS has its business address in Lillehammer.

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.