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

BOLIGCONSULT TAKST AS

Org. no. 928969665 Limited company (AS) Råde Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK −115,000
Equity NOK 124,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

BOLIGCONSULT TAKST AS is registered as a limited company in Råde, Østfold with organisation number 928969665. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Taksering av eiendommer og kjøp/salg og oppføring av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK −115,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK −115,000
Equity
NOK 124,000
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns BOLIGCONSULT TAKST AS?

BOLIGCONSULT AS
BOLIGCONSULT TAKST AS
NOK 1.2m rev. · NOK −115,000 profit

BOLIGCONSULT TAKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOLIGCONSULT TAKST AS

Who owns BOLIGCONSULT TAKST AS?

BOLIGCONSULT AS is the largest registered owner, with 100.0%.

What is the revenue of BOLIGCONSULT TAKST AS?

BOLIGCONSULT TAKST AS had revenue of NOK 1.2m in 2024.

Who is the general manager of BOLIGCONSULT TAKST AS?

Arnstein Mathisen is registered as general manager of BOLIGCONSULT TAKST AS.

Where is BOLIGCONSULT TAKST AS based?

BOLIGCONSULT TAKST AS has its business address in Råde.

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.