BIZTRAC BETA
Photographic activities

HALOLUDVIGSEN AS

Org. no. 914984068 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 836,000
Operating profit NOK 83,000
Equity NOK −55,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−55k kr).

HALOLUDVIGSEN AS is registered as a limited company in Oslo, Oslo with organisation number 914984068. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Reklame og portrettfotografering samt annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 836,000 in revenue and NOK 83,000 in operating profit.

Key figures · 2025

Revenue
NOK 836,000
Operating profit
NOK 83,000
Equity
NOK −55,000
Est. value
NOK 811,000

Financial health · 2025

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

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

Who owns HALOLUDVIGSEN AS?

JOHAN SEBASTIAN LUNDE LUDVIGSEN
HALOLUDVIGSEN AS
NOK 836,000 rev. · NOK 83,000 profit

HALOLUDVIGSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HALOLUDVIGSEN AS

Who owns HALOLUDVIGSEN AS?

JOHAN SEBASTIAN LUNDE LUDVIGSEN is the largest registered owner, with 100.0%.

What is the revenue of HALOLUDVIGSEN AS?

HALOLUDVIGSEN AS had revenue of NOK 836,000 in 2025.

Who is the general manager of HALOLUDVIGSEN AS?

Johan Sebastian Lunde Ludvigsen is registered as general manager of HALOLUDVIGSEN AS.

Where is HALOLUDVIGSEN AS based?

HALOLUDVIGSEN 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.