BIZTRAC BETA
Repair and maintenance of machinery

BRATLIE MASKINSERVICE AS

Org. no. 928222470 Limited company (AS) Nordre Follo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 12,000
Equity NOK 483,000
Incorporated 2021
Share capital NOK 30,000

BRATLIE MASKINSERVICE AS is registered as a limited company in Nordre Follo, Akershus with organisation number 928222470. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Montering og reparasjon av div. Serveringsmaskiner, automater og utstyr. Kjøp og salg av deler og utstyr som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 12,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 12,000
Equity
NOK 483,000
Est. value
NOK 313,000

Financial health · 2025

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

Who owns BRATLIE MASKINSERVICE AS?

VEGARD BRATLIE
BRATLIE MASKINSERVICE AS
NOK 1.4m rev. · NOK 12,000 profit

BRATLIE MASKINSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRATLIE MASKINSERVICE AS

Who owns BRATLIE MASKINSERVICE AS?

VEGARD BRATLIE is the largest registered owner, with 100.0%.

What is the revenue of BRATLIE MASKINSERVICE AS?

BRATLIE MASKINSERVICE AS had revenue of NOK 1.4m in 2025.

Who is the general manager of BRATLIE MASKINSERVICE AS?

Vegard Bratlie is registered as general manager of BRATLIE MASKINSERVICE AS.

Where is BRATLIE MASKINSERVICE AS based?

BRATLIE MASKINSERVICE AS has its business address in Ski.

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.