BIZTRAC BETA
Rental and operating of own or leased real estate

HUSEBO AS

Org. no. 919001844 Limited company (AS) Lørenskog Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 175,000
Operating profit NOK 150,000
Equity NOK 96,000
Incorporated 2017
Share capital NOK 30,000

HUSEBO AS is registered as a limited company in Lørenskog, Akershus with organisation number 919001844. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i og utvikling av fast eiendom, salg og utleie av fast eiendom, samt alt som står i forbindelse med dette, herunder å delta/investere i andre selskaper/aksjer med lignende virksomhet eller foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 175,000 in revenue and NOK 150,000 in operating profit.

Key figures · 2024

Revenue
NOK 175,000
Operating profit
NOK 150,000
Equity
NOK 96,000
Est. value
NOK 290,000

Financial health · 2024

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

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

Who owns HUSEBO AS?

ASK VEST BOLIG AS
HUSEBO AS
NOK 175,000 rev. · NOK 150,000 profit

HUSEBO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HUSEBO AS

Who owns HUSEBO AS?

ASK VEST BOLIG AS is the largest registered owner, with 100.0%.

What is the revenue of HUSEBO AS?

HUSEBO AS had revenue of NOK 175,000 in 2024.

Who is the general manager of HUSEBO AS?

Brede Gunnar Huser is registered as general manager of HUSEBO AS.

Where is HUSEBO AS based?

HUSEBO AS has its business address in Lørenskog.

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.