biztrac. BETA
COMPANY REGISTER PROFILE
936228925 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Civil engineering activities

BEG AS

Org. no. 936228925 Limited company (AS) Narvik Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 10,000
Operating profit NOK −18,000
Equity NOK 16,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

BEG AS is registered as a limited company in Narvik, Nordland with organisation number 936228925. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rådgivning og prosjektering for byggeprosjekter, samt taksering og verdivurdering av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 10,000 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 10,000
Operating profit
NOK −18,000
Equity
NOK 16,000
Est. value
NOK 19,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BEG AS?

BEG AS
NOK 10,000 rev. · NOK −18,000 profit

BEG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BEG AS er morselskap for 1 datterselskap:

Frequently asked questions about BEG AS

Who owns BEG AS?

Espen Gamst is the largest registered owner, with 100.0%.

What is the revenue of BEG AS?

BEG AS had revenue of NOK 10,000 in 2025.

Who is the general manager of BEG AS?

Espen Gamst is registered as general manager of BEG AS.

Where is BEG AS based?

BEG AS has its business address in Narvik.

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.