BIZTRAC BETA
Other specialised construction activities n.e.c.

SAG & BORETEKNIKK AS

Org. no. 932190141 Limited company (AS) Ørland Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 8,000
Equity NOK 431,000
Incorporated 2023
Share capital NOK 300,000

SAG & BORETEKNIKK AS is registered as a limited company in Ørland, Trøndelag with organisation number 932190141. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2023. Registered share capital is NOK 300,000, divided into 3000 shares. The company's stated purpose is: “Kjerneboring, betongsaging og anleggsvirksomhet som naturlig hører sammen med dette. Selskapet kan engasjere seg i annen virksomhet ved aksjekjøp eller lignende.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 8,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 8,000
Equity
NOK 431,000
Est. value
NOK 212,000

Financial health · 2024

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

Who owns SAG & BORETEKNIKK AS?

RONNY VALBEKMO
SAG & BORETEKNIKK AS
NOK 1.6m rev. · NOK 8,000 profit

SAG & BORETEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SAG & BORETEKNIKK AS

Who owns SAG & BORETEKNIKK AS?

RONNY VALBEKMO is the largest registered owner, with 100.0%.

What is the revenue of SAG & BORETEKNIKK AS?

SAG & BORETEKNIKK AS had revenue of NOK 1.6m in 2024.

Who is the general manager of SAG & BORETEKNIKK AS?

Ronny Valbekmo is registered as general manager of SAG & BORETEKNIKK AS.

Where is SAG & BORETEKNIKK AS based?

SAG & BORETEKNIKK AS has its business address in Brekstad.

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.