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

WP TAKST OG EIENDOM AS

Org. no. 831673362 Limited company (AS) Lørenskog Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK 25,000
Equity NOK 99,000
Incorporated 2023
Share capital NOK 30,000

WP TAKST OG EIENDOM AS is registered as a limited company in Lørenskog, Akershus with organisation number 831673362. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Taksering av eiendom og kjøp og salg av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK 25,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK 25,000
Equity
NOK 99,000
Est. value
NOK 110,000

Financial health · 2024

Liquidity
1.00
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns WP TAKST OG EIENDOM AS?

BROR WERNER WERENSKIOLD
WP TAKST OG EIENDOM AS
NOK 1.9m rev. · NOK 25,000 profit

WP TAKST OG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WP TAKST OG EIENDOM AS

Who owns WP TAKST OG EIENDOM AS?

BROR WERNER WERENSKIOLD is the largest registered owner, with 100.0%.

What is the revenue of WP TAKST OG EIENDOM AS?

WP TAKST OG EIENDOM AS had revenue of NOK 1.9m in 2024.

Who is the general manager of WP TAKST OG EIENDOM AS?

Bror Werner Werenskiold is registered as general manager of WP TAKST OG EIENDOM AS.

Where is WP TAKST OG EIENDOM AS based?

WP TAKST OG EIENDOM AS has its business address in Fjellhamar.

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.