biztrac. BETA
COMPANY REGISTER PROFILE
916721153 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Site preparation

BREVIK AS

Org. no. 916721153 Limited company (AS) Lier Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 139.4m
Operating profit NOK 615,000
Equity NOK 25.7m
Incorporated 2016
Employees 42
Share capital NOK 640,000

BREVIK AS is registered as a limited company in Lier, Buskerud with organisation number 916721153. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2016 and has 42 registered employees. Registered share capital is NOK 640,000, divided into 100 shares. The company's stated purpose is: “Maskinentreprenørvirksomhet, herunder graving og transport samt annen virksomhet som naturlig står i forbindelse med dette herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 139.4m in revenue and NOK 615,000 in operating profit.

Former names: KNUT A. BREVIK DRIFT AS

Key figures · 2025

Revenue
NOK 139.4m
▼ −20 %
Operating profit
NOK 615,000
▼ −91 %
Equity
NOK 25.7m
▲ +3 %
Est. value
NOK 21.0m

Financial health · 2025

Liquidity
1.85
Good
Current assets ÷ current liabilities
Profitability
1.9%
Weak
Return on total assets
Solidity
44.4%
Very good
Equity as a share of total capital

Who owns BREVIK AS?

BREVIK AS
NOK 139.4m rev. · NOK 615,000 profit

BREVIK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BREVIK AS

Who owns BREVIK AS?

BREVIK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BREVIK AS?

BREVIK AS had revenue of NOK 139.4m in 2025.

Who is the general manager of BREVIK AS?

Anders Brevik is registered as general manager of BREVIK AS.

Where is BREVIK AS based?

BREVIK AS has its business address in Lierskogen.

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.