biztrac. BETA
COMPANY REGISTER PROFILE
919271000 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Masonry and bricklaying activities

OLAV MAGNE GORSETH AS

Org. no. 919271000 Limited company (AS) Trondheim Incorporated 2017 Active
Revenue 2025 NOK 231,000
Operating profit NOK 3,000
Equity NOK −52,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−52k kr).

OLAV MAGNE GORSETH AS is registered as a limited company in Trondheim, Trøndelag with organisation number 919271000. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Murervirksomhet og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 231,000 in revenue and NOK 3,000 in operating profit.

Key figures · 2025

Revenue
NOK 231,000
▼ −74 %
Operating profit
NOK 3,000
▲ +101 %
Equity
NOK −52,000
▼ −15 %

Financial health · 2025

Liquidity
0.78
Weak
Current assets ÷ current liabilities
Profitability
1.5%
Weak
Return on total assets
Solidity
-28.2%
Weak
Equity as a share of total capital

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

Who owns OLAV MAGNE GORSETH AS?

OLAV MAGNE GORSETH AS
NOK 231,000 rev. · NOK 3,000 profit

OLAV MAGNE GORSETH AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLAV MAGNE GORSETH AS

Who owns OLAV MAGNE GORSETH AS?

Olav Magne Gorseth is the largest registered owner, with 100.0%.

What is the revenue of OLAV MAGNE GORSETH AS?

OLAV MAGNE GORSETH AS had revenue of NOK 231,000 in 2025.

Where is OLAV MAGNE GORSETH AS based?

OLAV MAGNE GORSETH AS has its business address in Trondheim.

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.