BIZTRAC BETA
Other technical consultancy

BYGGTEK RØROS AS

Org. no. 935482798 Limited company (AS) Røros Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 491,000
Operating profit NOK 2,000
Equity NOK 96,000
Incorporated 2025
Share capital NOK 100,000

BYGGTEK RØROS AS is registered as a limited company in Røros, Trøndelag with organisation number 935482798. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2025. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Selge varer og tjenester innen ingeniørarbeid og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 491,000 in revenue and NOK 2,000 in operating profit.

Key figures · 2025

Revenue
NOK 491,000
Operating profit
NOK 2,000
Equity
NOK 96,000
Est. value
NOK 61,000

Financial health · 2025

Liquidity
1.92
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
48.0%
Weak
Equity as a share of total capital

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

Who owns BYGGTEK RØROS AS?

MARTIN HOPSTAD GRANERUD
BYGGTEK RØROS AS
NOK 491,000 rev. · NOK 2,000 profit

BYGGTEK RØROS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGGTEK RØROS AS

Who owns BYGGTEK RØROS AS?

MARTIN HOPSTAD GRANERUD is the largest registered owner, with 100.0%.

What is the revenue of BYGGTEK RØROS AS?

BYGGTEK RØROS AS had revenue of NOK 491,000 in 2025.

Who is the general manager of BYGGTEK RØROS AS?

Martin Hopstad Granerud is registered as general manager of BYGGTEK RØROS AS.

Where is BYGGTEK RØROS AS based?

BYGGTEK RØROS AS has its business address in Røros.

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.