biztrac. BETA
COMPANY REGISTER PROFILE
889197242 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

MARTIN BØHLER AS

Org. no. 889197242 Limited company (AS) Indre Østfold Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −62,000
Equity NOK 18.1m
Incorporated 2005
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−62k kr).
  • Nylig endring 2026-09-23 Adresseendring registrert 2026-09-23.

MARTIN BØHLER AS is registered as a limited company in Indre Østfold, Østfold with organisation number 889197242. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Deltakelse i andre selskap, rådgivningsvirksomhet og forvaltning av selskapets kapital gjennom annen investering og utlån.”.

Key figures · 2025

Operating profit
NOK −62,000
▲ +34 %
Equity
NOK 18.1m
▲ +8 %
Est. value
NOK 14.7m

Financial health · 2025

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

Who owns MARTIN BØHLER AS?

MARTIN BØHLER AS
· NOK −62,000 profit

MARTIN BØHLER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MARTIN BØHLER AS own?

MARTIN BØHLER AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about MARTIN BØHLER AS

Who owns MARTIN BØHLER AS?

Martin Bøhler is the largest registered owner, with 100.0%.

Who is the general manager of MARTIN BØHLER AS?

Martin Bøhler is registered as general manager of MARTIN BØHLER AS.

Where is MARTIN BØHLER AS based?

MARTIN BØHLER AS has its business address in Spydeberg.

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.