BIZTRAC BETA
Other real estate activities on a fee or contract basis

BYGGTAKST ELVERUM AS

Org. no. 990646562 Limited company (AS) Elverum Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 5.3m
Operating profit NOK 58,000
Equity NOK 1.5m
Incorporated 2006
Employees 7
Share capital NOK 100,000

BYGGTAKST ELVERUM AS is registered as a limited company in Elverum, Innlandet with organisation number 990646562. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2006 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Taksteringsvirksomhet og annen konsulentvirksomhet innen bygg og anlegg, samt det som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.3m in revenue and NOK 58,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.3m
Operating profit
NOK 58,000
Equity
NOK 1.5m
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
2.26
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
58.8%
Very good
Equity as a share of total capital

Who owns BYGGTAKST ELVERUM AS?

KNUT ROGER FURUSETH
BYGGTAKST ELVERUM AS
NOK 5.3m rev. · NOK 58,000 profit

BYGGTAKST ELVERUM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BYGGTAKST ELVERUM AS

Who owns BYGGTAKST ELVERUM AS?

KNUT ROGER FURUSETH is the largest registered owner, with 50.0%.

What is the revenue of BYGGTAKST ELVERUM AS?

BYGGTAKST ELVERUM AS had revenue of NOK 5.3m in 2025.

Who is the general manager of BYGGTAKST ELVERUM AS?

Knut Roger Furuseth is registered as general manager of BYGGTAKST ELVERUM AS.

Where is BYGGTAKST ELVERUM AS based?

BYGGTAKST ELVERUM AS has its business address in Elverum.

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.