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

BOLIGTAKST AS

Org. no. 989016237 Limited company (AS) Kristiansand Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 3.7m
Operating profit NOK 1.1m
Equity NOK 2.2m
Incorporated 2005
Share capital NOK 100,000

BOLIGTAKST AS is registered as a limited company in Kristiansand, Agder with organisation number 989016237. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Taksering av boligeiendommer, byggeledelse, utførelse av mur- og betongarbeider samt varehandel i denne forbindelse, investering i annen virksomhet, herunder delta i andre selskaper som aksjeeier eller ansvarlig deltaker samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.7m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 3.7m
Operating profit
NOK 1.1m
Equity
NOK 2.2m
Est. value
NOK 3.6m

Financial health · 2025

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

Who owns BOLIGTAKST AS?

SVEN BENTSEN
BOLIGTAKST AS
NOK 3.7m rev. · NOK 1.1m profit

BOLIGTAKST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BOLIGTAKST AS own?

BOLIGTAKST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BOLIGTAKST AS

Who owns BOLIGTAKST AS?

SVEN BENTSEN is the largest registered owner, with 100.0%.

What is the revenue of BOLIGTAKST AS?

BOLIGTAKST AS had revenue of NOK 3.7m in 2025.

Where is BOLIGTAKST AS based?

BOLIGTAKST AS has its business address in Kristiansand S.

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.