BIZTRAC BETA
Other technical consultancy

MONTØRTECH LÅS OG BESLAG AS

Org. no. 922777411 Limited company (AS) Nordre Follo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK 16,000
Equity NOK 266,000
Incorporated 2019
Share capital NOK 30,000

MONTØRTECH LÅS OG BESLAG AS is registered as a limited company in Nordre Follo, Akershus with organisation number 922777411. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Salg, montering og service på alt av lås og beslag og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.9m in revenue and NOK 16,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
Operating profit
NOK 16,000
Equity
NOK 266,000
Est. value
NOK 211,000

Financial health · 2025

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

Who owns MONTØRTECH LÅS OG BESLAG AS?

CHRISTIAN ANDERSEN
MONTØRTECH LÅS OG BESLAG AS
NOK 3.9m rev. · NOK 16,000 profit

MONTØRTECH LÅS OG BESLAG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MONTØRTECH LÅS OG BESLAG AS

Who owns MONTØRTECH LÅS OG BESLAG AS?

CHRISTIAN ANDERSEN is the largest registered owner, with 85.0%.

What is the revenue of MONTØRTECH LÅS OG BESLAG AS?

MONTØRTECH LÅS OG BESLAG AS had revenue of NOK 3.9m in 2025.

Who is the general manager of MONTØRTECH LÅS OG BESLAG AS?

Christian Andersen is registered as general manager of MONTØRTECH LÅS OG BESLAG AS.

Where is MONTØRTECH LÅS OG BESLAG AS based?

MONTØRTECH LÅS OG BESLAG AS has its business address in Langhus.

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.