biztrac. BETA
COMPANY REGISTER PROFILE
931312472 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

AS SUNNANBRUKET

Org. no. 931312472 Limited company (AS) Namsos Incorporated 1916 Active
Ownership graph ↗
Revenue 2025 NOK 6,000
Operating profit NOK −46,000
Equity NOK 360,000
Incorporated 1916
Share capital NOK 102,000

Signals

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

AS SUNNANBRUKET is registered as a limited company in Namsos, Trøndelag with organisation number 931312472. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 1916. Registered share capital is NOK 102,000, divided into 35 shares. The company's stated purpose is: “Forvalte eiendommene Øksnesøya og Henningen Midtre til beste for aksjonærene.”. The most recent filed accounts, for the 2025 financial year, show NOK 6,000 in revenue and NOK −46,000 in operating profit.

Key figures · 2025

Revenue
NOK 6,000
▲ +3 %
Operating profit
NOK −46,000
▼ −1492 %
Equity
NOK 360,000
▼ −10 %
Est. value
NOK 256,000

Financial health · 2025

Liquidity
8.80
Very good
Current assets ÷ current liabilities
Profitability
-7.2%
Not satisfactory
Return on total assets
Solidity
92.2%
Very good
Equity as a share of total capital

Who owns AS SUNNANBRUKET?

AS SUNNANBRUKET has 16 registered shareholders:

All shareholders and roles →

Frequently asked questions about AS SUNNANBRUKET

Who owns AS SUNNANBRUKET?

Ole Mørkved is the largest registered owner, with 22.9%.

What is the revenue of AS SUNNANBRUKET?

AS SUNNANBRUKET had revenue of NOK 6,000 in 2025.

Who is the general manager of AS SUNNANBRUKET?

Mathias Mørkved is registered as general manager of AS SUNNANBRUKET.

Where is AS SUNNANBRUKET based?

AS SUNNANBRUKET has its business address in Namsos.

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

Report a problem

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