BIZTRAC BETA
Accounting and bookkeeping

HAMA ACCOUNTING AS

Org. no. 822866182 Limited company (AS) Lørenskog Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 8.9m
Operating profit NOK 721,000
Equity NOK 775,000
Incorporated 2019
Employees 6
Share capital NOK 30,000

HAMA ACCOUNTING AS is registered as a limited company in Lørenskog, Akershus with organisation number 822866182. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2019 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Levere regnskaps-, økonomi- og konsulenttjenester, samt alt som står i forbindelse med dette, herunder deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.9m in revenue and NOK 721,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.9m
Operating profit
NOK 721,000
Equity
NOK 775,000
Est. value
NOK 4.0m

Financial health · 2025

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

Who owns HAMA ACCOUNTING AS?

HANS LUDVIGSEN HOLDING AS
HAMA ACCOUNTING AS
NOK 8.9m rev. · NOK 721,000 profit

HAMA ACCOUNTING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAMA ACCOUNTING AS

Who owns HAMA ACCOUNTING AS?

HANS LUDVIGSEN HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of HAMA ACCOUNTING AS?

HAMA ACCOUNTING AS had revenue of NOK 8.9m in 2025.

Who is the general manager of HAMA ACCOUNTING AS?

Hans Ludvig Lund is registered as general manager of HAMA ACCOUNTING AS.

Where is HAMA ACCOUNTING AS based?

HAMA ACCOUNTING 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.