BIZTRAC BETA
COMPANY REGISTER PROFILE
879903432 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Non-specialised retail sale of predominately food, beverages or tobacco

MATHUSET EGERSUND AS

Org. no. 879903432 Limited company (AS) Eigersund Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 54.4m
Operating profit NOK 1.8m
Equity NOK 6.0m
Incorporated 1998
Share capital NOK 150,000

MATHUSET EGERSUND AS is registered as a limited company in Eigersund, Rogaland with organisation number 879903432. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 1998. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Dagligvarebutikk.”. The most recent filed accounts, for the 2025 financial year, show NOK 54.4m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 54.4m
▼ −2 %
Operating profit
NOK 1.8m
▼ −23 %
Equity
NOK 6.0m
▲ +50 %
Est. value
NOK 11.0m

Financial health · 2025

Liquidity
0.96
Weak
Current assets ÷ current liabilities
Profitability
32.0%
Very good
Return on total assets
Solidity
62.7%
Very good
Equity as a share of total capital

Who owns MATHUSET EGERSUND AS?

MATHUSET EGERSUND AS
NOK 54.4m rev. · NOK 1.8m profit

MATHUSET EGERSUND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MATHUSET EGERSUND AS

Who owns MATHUSET EGERSUND AS?

SMART EIENDOM EGERSUND AS is the largest registered owner, with 100.0%.

What is the revenue of MATHUSET EGERSUND AS?

MATHUSET EGERSUND AS had revenue of NOK 54.4m in 2025.

Who is the general manager of MATHUSET EGERSUND AS?

Frank Robert Remme is registered as general manager of MATHUSET EGERSUND AS.

Where is MATHUSET EGERSUND AS based?

MATHUSET EGERSUND AS has its business address in Egersund.

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.