BIZTRAC BETA
Rental and operating of own or leased real estate

BLAASENBORG HOLDING AS

Org. no. 994656813 Limited company (AS) Trondheim Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 976,000
Operating profit NOK 733,000
Equity NOK 20.2m
Incorporated 2009
Share capital NOK 100,000

BLAASENBORG HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 994656813. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av egen fast eiendom og annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 976,000 in revenue and NOK 733,000 in operating profit.

Key figures · 2024

Revenue
NOK 976,000
Operating profit
NOK 733,000
Equity
NOK 20.2m
Est. value
NOK 15.5m

Financial health · 2024

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

Who owns BLAASENBORG HOLDING AS?

HANS PETTER WISTH
BLAASENBORG HOLDING AS
NOK 976,000 rev. · NOK 733,000 profit

BLAASENBORG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BLAASENBORG HOLDING AS own?

BLAASENBORG HOLDING AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about BLAASENBORG HOLDING AS

Who owns BLAASENBORG HOLDING AS?

HANS PETTER WISTH is the largest registered owner, with 100.0%.

What is the revenue of BLAASENBORG HOLDING AS?

BLAASENBORG HOLDING AS had revenue of NOK 976,000 in 2024.

Where is BLAASENBORG HOLDING AS based?

BLAASENBORG HOLDING AS has its business address in Trondheim.

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.