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

RØROS TAKST AS

Org. no. 915224466 Limited company (AS) Røros Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 303,000
Equity NOK 480,000
Incorporated 2015
Share capital NOK 30,000

RØROS TAKST AS is registered as a limited company in Røros, Trøndelag with organisation number 915224466. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Taksering av fast eiendom, bygningsrådgivning og annet som naturlig faller sammen med dette. Selskapets virksomhet omfatter også investering i fast eiendom og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 303,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 303,000
Equity
NOK 480,000
Est. value
NOK 911,000

Financial health · 2025

Liquidity
0.19
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.2%
Weak
Equity as a share of total capital

Who owns RØROS TAKST AS?

OLE ERIK NILSGÅRD FERAGEN
RØROS TAKST AS
NOK 1.4m rev. · NOK 303,000 profit

RØROS TAKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RØROS TAKST AS

Who owns RØROS TAKST AS?

OLE ERIK NILSGÅRD FERAGEN is the largest registered owner, with 100.0%.

What is the revenue of RØROS TAKST AS?

RØROS TAKST AS had revenue of NOK 1.4m in 2024.

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

Ole Erik Nilsgård Feragen is registered as general manager of RØROS TAKST AS.

Where is RØROS TAKST AS based?

RØROS TAKST 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.