BIZTRAC BETA
Rental and operating of own or leased real estate

BAME INVEST AS

Org. no. 990055912 Limited company (AS) Asker Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 670,000
Operating profit NOK 631,000
Equity NOK 430,000
Incorporated 2006
Share capital NOK 105,000

BAME INVEST AS is registered as a limited company in Asker, Akershus with organisation number 990055912. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 105,000, divided into 26217 shares. The company's stated purpose is: “Kjøp, salg, investering i aksjer og andre verdipapirer samt investering i fast eiendom med dertil tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 670,000 in revenue and NOK 631,000 in operating profit.

Key figures · 2025

Revenue
NOK 670,000
Operating profit
NOK 631,000
Equity
NOK 430,000
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns BAME INVEST AS?

ARNE LUTHER
BAME INVEST AS
NOK 670,000 rev. · NOK 631,000 profit

BAME INVEST AS has 3 registered shareholders:

All shareholders and roles →

Which companies does BAME INVEST AS own?

BAME INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BAME INVEST AS

Who owns BAME INVEST AS?

ARNE LUTHER is the largest registered owner, with 69.0%.

What is the revenue of BAME INVEST AS?

BAME INVEST AS had revenue of NOK 670,000 in 2025.

Who is the general manager of BAME INVEST AS?

Arne Luther is registered as general manager of BAME INVEST AS.

Where is BAME INVEST AS based?

BAME INVEST AS has its business address in Tofte.

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.