biztrac. BETA
COMPANY REGISTER PROFILE
950716290 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

TAKSTSENTERET AS

Org. no. 950716290 Limited company (AS) Bærum Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK −15,000
Equity NOK 210,000
Incorporated 1989
Share capital NOK 120,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−15k kr).

TAKSTSENTERET AS is registered as a limited company in Bærum, Akershus with organisation number 950716290. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 1989. Registered share capital is NOK 120,000, divided into 120 shares. The company's stated purpose is: “Taksering og konsulentvirksomhet, handel samt alt hva derved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
▼ −6 %
Operating profit
NOK −15,000
▼ −145 %
Equity
NOK 210,000
▼ −1 %
Est. value
NOK 2.2m

Financial health · 2025

Liquidity
3.31
Very good
Current assets ÷ current liabilities
Profitability
0.5%
Not satisfactory
Return on total assets
Solidity
69.7%
Very good
Equity as a share of total capital

Who owns TAKSTSENTERET AS?

TAKSTSENTERET AS has 8 registered shareholders:

All shareholders and roles →

Frequently asked questions about TAKSTSENTERET AS

Who owns TAKSTSENTERET AS?

Helge Jensen is the largest registered owner, with 12.5%.

What is the revenue of TAKSTSENTERET AS?

TAKSTSENTERET AS had revenue of NOK 1.4m in 2025.

Who is the general manager of TAKSTSENTERET AS?

Helge Jensen is registered as general manager of TAKSTSENTERET AS.

Where is TAKSTSENTERET AS based?

TAKSTSENTERET AS has its business address in Stabekk.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.