BIZTRAC BETA
Site preparation

BEK MASKIN AS

Org. no. 997141725 Limited company (AS) Nordreisa Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK −242,000
Equity NOK 2.2m
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−242k kr).

BEK MASKIN AS is registered as a limited company in Nordreisa, Troms with organisation number 997141725. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utføre oppdrag innenfor bygg og anlegg, entreprenørvirksomhet. Selskapet må også ha muligheten til å drive annen handelsvirksomhet som er til det beste for aksjonærene, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK −242,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK −242,000
Equity
NOK 2.2m
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns BEK MASKIN AS?

BØRT-ERIK KRISTOFFERSEN
BEK MASKIN AS
NOK 2.0m rev. · NOK −242,000 profit

BEK MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BEK MASKIN AS

Who owns BEK MASKIN AS?

BØRT-ERIK KRISTOFFERSEN is the largest registered owner, with 100.0%.

What is the revenue of BEK MASKIN AS?

BEK MASKIN AS had revenue of NOK 2.0m in 2025.

Who is the general manager of BEK MASKIN AS?

Børt-Erik Kristoffersen is registered as general manager of BEK MASKIN AS.

Where is BEK MASKIN AS based?

BEK MASKIN AS has its business address in Storslett.

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.