BIZTRAC BETA
Masonry and bricklaying activities

AS MAGNOR BYGG

Org. no. 952557890 Limited company (AS) Eidskog Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 745,000
Operating profit NOK −48,000
Equity NOK 30,000
Incorporated 1989
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−48k kr).

AS MAGNOR BYGG is registered as a limited company in Eidskog, Innlandet with organisation number 952557890. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 1989. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Oppføring av bygg, restaurering, murerarbeid og alt som berved står i forbindeise samt også deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 745,000 in revenue and NOK −48,000 in operating profit.

Key figures · 2024

Revenue
NOK 745,000
Operating profit
NOK −48,000
Equity
NOK 30,000
Est. value
NOK 272,000

Financial health · 2024

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

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

Who owns AS MAGNOR BYGG?

SVEIN ERIK RØHR
AS MAGNOR BYGG
NOK 745,000 rev. · NOK −48,000 profit

AS MAGNOR BYGG has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AS MAGNOR BYGG

Who owns AS MAGNOR BYGG?

SVEIN ERIK RØHR is the largest registered owner, with 100.0%.

What is the revenue of AS MAGNOR BYGG?

AS MAGNOR BYGG had revenue of NOK 745,000 in 2024.

Who is the general manager of AS MAGNOR BYGG?

Tom Fredrik Røhr is registered as general manager of AS MAGNOR BYGG.

Where is AS MAGNOR BYGG based?

AS MAGNOR BYGG has its business address in Magnor.

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.