biztrac. BETA
COMPANY REGISTER PROFILE
934348869 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

FIRE CONTROL BERGEN AS

Org. no. 934348869 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 211,000
Equity NOK 181,000
Incorporated 2024
Share capital NOK 30,000

FIRE CONTROL BERGEN AS is registered as a limited company in Bergen, Vestland with organisation number 934348869. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utvikling, service og salg av produkter innen brannslukning og sikkerhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 211,000 in operating profit.

Former names: MOTORVEI AS

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 211,000
Equity
NOK 181,000
Est. value
NOK 992,000

Financial health · 2025

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
20.5%
Good
Equity as a share of total capital

Who owns FIRE CONTROL BERGEN AS?

FIRE CONTROL BERGEN AS
NOK 1.1m rev. · NOK 211,000 profit

FIRE CONTROL BERGEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FIRE CONTROL BERGEN AS

Who owns FIRE CONTROL BERGEN AS?

TEVA HOLDING AS is the largest registered owner, with 80.0%.

What is the revenue of FIRE CONTROL BERGEN AS?

FIRE CONTROL BERGEN AS had revenue of NOK 1.1m in 2025.

Who is the general manager of FIRE CONTROL BERGEN AS?

Thomas Andre Tellefsen is registered as general manager of FIRE CONTROL BERGEN AS.

Where is FIRE CONTROL BERGEN AS based?

FIRE CONTROL BERGEN AS has its business address in Fyllingsdalen.

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.