BIZTRAC BETA
Site preparation

A. BRUFJELL HOLDING & INVEST AS

Org. no. 933724417 Limited company (AS) Birkenes Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 493,000
Equity NOK 446,000
Incorporated 2024
Share capital NOK 30,000

A. BRUFJELL HOLDING & INVEST AS is registered as a limited company in Birkenes, Agder with organisation number 933724417. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Maskinentreprenør og utleie av arbeidskraft herunder investering i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 493,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 493,000
Equity
NOK 446,000
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns A. BRUFJELL HOLDING & INVEST AS?

ANDRÉ BRUFJELL
A. BRUFJELL HOLDING & INVEST AS
NOK 2.9m rev. · NOK 493,000 profit

A. BRUFJELL HOLDING & INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about A. BRUFJELL HOLDING & INVEST AS

Who owns A. BRUFJELL HOLDING & INVEST AS?

ANDRÉ BRUFJELL is the largest registered owner, with 100.0%.

What is the revenue of A. BRUFJELL HOLDING & INVEST AS?

A. BRUFJELL HOLDING & INVEST AS had revenue of NOK 2.9m in 2025.

Who is the general manager of A. BRUFJELL HOLDING & INVEST AS?

André Brufjell is registered as general manager of A. BRUFJELL HOLDING & INVEST AS.

Where is A. BRUFJELL HOLDING & INVEST AS based?

A. BRUFJELL HOLDING & INVEST AS has its business address in Vatnestrøm.

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.