BIZTRAC BETA
COMPANY REGISTER PROFILE
990466831 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Other recreational activities

LEKELAND 1 HAMAR AS

Org. no. 990466831 Limited company (AS) Hamar Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 6.7m
Operating profit NOK 784,000
Equity NOK 317,000
Incorporated 2006
Employees 17
Share capital NOK 100,000

LEKELAND 1 HAMAR AS is registered as a limited company in Hamar, Innlandet with organisation number 990466831. The business is classified under other recreational activities (NACE 93.292). The company was incorporated in 2006 and has 17 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Underholdning og det som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.7m in revenue and NOK 784,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.7m
▼ −5 %
Operating profit
NOK 784,000
▼ −28 %
Equity
NOK 317,000
▲ +5 %
Est. value
NOK 3.9m

Financial health · 2025

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
46.0%
Very good
Return on total assets
Solidity
19.6%
Good
Equity as a share of total capital

Who owns LEKELAND 1 HAMAR AS?

LEKELAND 1 HAMAR AS
NOK 6.7m rev. · NOK 784,000 profit

LEKELAND 1 HAMAR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEKELAND 1 HAMAR AS

Who owns LEKELAND 1 HAMAR AS?

BOWLING 1 HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LEKELAND 1 HAMAR AS?

LEKELAND 1 HAMAR AS had revenue of NOK 6.7m in 2025.

Who is the general manager of LEKELAND 1 HAMAR AS?

Ståle Emanuel Johansen is registered as general manager of LEKELAND 1 HAMAR AS.

Where is LEKELAND 1 HAMAR AS based?

LEKELAND 1 HAMAR AS has its business address in Hamar.

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.