BIZTRAC BETA
Repair and maintenance of motor vehicles

BREKKES GUMMISERVICE AS

Org. no. 927279754 Limited company (AS) Fauske Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK 141,000
Equity NOK 369,000
Incorporated 2021
Share capital NOK 200,000

BREKKES GUMMISERVICE AS is registered as a limited company in Fauske, Nordland with organisation number 927279754. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2021. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Verksted for dekkomlegging, dekkhotell og salg av andre produkter/tjenester som naturlig hører til dette. Brøyting og graving samt produksjon og salg av ved.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK 141,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
Operating profit
NOK 141,000
Equity
NOK 369,000
Est. value
NOK 655,000

Financial health · 2025

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

Who owns BREKKES GUMMISERVICE AS?

KJELL OVE BREKKE
BREKKES GUMMISERVICE AS
NOK 3.8m rev. · NOK 141,000 profit

BREKKES GUMMISERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BREKKES GUMMISERVICE AS

Who owns BREKKES GUMMISERVICE AS?

KJELL OVE BREKKE is the largest registered owner, with 100.0%.

What is the revenue of BREKKES GUMMISERVICE AS?

BREKKES GUMMISERVICE AS had revenue of NOK 3.8m in 2025.

Who is the general manager of BREKKES GUMMISERVICE AS?

Marius Aspli Brekke is registered as general manager of BREKKES GUMMISERVICE AS.

Where is BREKKES GUMMISERVICE AS based?

BREKKES GUMMISERVICE AS has its business address in Fauske.

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.