biztrac. BETA
COMPANY REGISTER PROFILE
934177061 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

BLOMLIE ARNTSEN AS

Org. no. 934177061 Limited company (AS) Trondheim Incorporated 2024 Active
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

BLOMLIE ARNTSEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 934177061. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investere i, eie, forvalte og selge andeler i andre selskaper, samt å utøve aktiviteter som er komplementære til disse, inkludert, men ikke begrenset til, finansiell rådgivning og forvaltning.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 24,000
Est. value
NOK 28,000

Financial health · 2025

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

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

Who owns BLOMLIE ARNTSEN AS?

BLOMLIE ARNTSEN AS
NOK 0 rev. · NOK 0 profit

BLOMLIE ARNTSEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BLOMLIE ARNTSEN AS own?

BLOMLIE ARNTSEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BLOMLIE ARNTSEN AS

Who owns BLOMLIE ARNTSEN AS?

Jørgen Arntsen is the largest registered owner, with 50.0%.

What is the revenue of BLOMLIE ARNTSEN AS?

BLOMLIE ARNTSEN AS had revenue of NOK 0 in 2025.

Where is BLOMLIE ARNTSEN AS based?

BLOMLIE ARNTSEN AS has its business address in Heimdal.

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

Report a problem

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