BIZTRAC BETA
COMPANY REGISTER PROFILE
934502612 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

HUSBY FINANCE AS

Org. no. 934502612 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −662,000
Equity NOK 18.6m
Incorporated 2024
Share capital NOK 1.4m

Signals

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

HUSBY FINANCE AS is registered as a limited company in Oslo, Oslo with organisation number 934502612. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 1.4m, divided into 1375 shares. The company's stated purpose is: “Å drive investeringsvirksomhet.”.

Key figures · 2025

Operating profit
NOK −662,000
Equity
NOK 18.6m
Est. value
NOK 10.1m

Financial health · 2025

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

Who owns HUSBY FINANCE AS?

HUSBY FINANCE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HUSBY FINANCE AS

Who owns HUSBY FINANCE AS?

OTTO EDVARD HUSBY KALVØ is the largest registered owner, with 60.0%.

Who is the general manager of HUSBY FINANCE AS?

Otto Edvard Husby Kalvø is registered as general manager of HUSBY FINANCE AS.

Where is HUSBY FINANCE AS based?

HUSBY FINANCE AS has its business address in Oslo.

Property

Business address Sollerudveien 25E, 0283 Oslo
Cadastral unit 301-9/537/0/0
Building Enebolig · 1 unit

8 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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