BIZTRAC BETA
COMPANY REGISTER PROFILE
926334417 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Construction of residential and non-residential buildings

HUSBYGGERNE AS

Org. no. 926334417 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 358,000
Equity NOK 199,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-07-08 Adresseendring registrert 2026-07-08.

HUSBYGGERNE AS is registered as a limited company in Oslo, Oslo with organisation number 926334417. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Bygging av boliger og øvrige snekkeroppdrag, og det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 358,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 358,000
Equity
NOK 199,000
Est. value
NOK 1.1m

Financial health · 2024

Liquidity
1.41
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.2%
Good
Equity as a share of total capital

Who owns HUSBYGGERNE AS?

JOHN OPSAHL
HUSBYGGERNE AS
NOK 2.5m rev. · NOK 358,000 profit

HUSBYGGERNE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HUSBYGGERNE AS

Who owns HUSBYGGERNE AS?

JOHN OPSAHL is the largest registered owner, with 100.0%.

What is the revenue of HUSBYGGERNE AS?

HUSBYGGERNE AS had revenue of NOK 2.5m in 2024.

Who is the general manager of HUSBYGGERNE AS?

John Opsahl is registered as general manager of HUSBYGGERNE AS.

Where is HUSBYGGERNE AS based?

HUSBYGGERNE AS has its business address in Oslo.

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.