biztrac. BETA
COMPANY REGISTER PROFILE
912891232 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Support services to forestry

AKSNES & BRATTLI SKOG OG MASKIN AS

Org. no. 912891232 Limited company (AS) Kvam Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 10.9m
Operating profit NOK 882,000
Equity NOK 3.1m
Incorporated 2013
Employees 6
Share capital NOK 100,000

AKSNES & BRATTLI SKOG OG MASKIN AS is registered as a limited company in Kvam, Vestland with organisation number 912891232. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2013 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Skogsarbeid, brøyting og anna anleggsarbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.9m in revenue and NOK 882,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.9m
▲ +23 %
Operating profit
NOK 882,000
▲ +60 %
Equity
NOK 3.1m
▲ +28 %
Est. value
NOK 4.8m

Financial health · 2025

Liquidity
2.19
Very good
Current assets ÷ current liabilities
Profitability
20.0%
Very good
Return on total assets
Solidity
65.3%
Very good
Equity as a share of total capital

Who owns AKSNES & BRATTLI SKOG OG MASKIN AS?

AKSNES & BRATTLI SKOG OG MASKIN AS
NOK 10.9m rev. · NOK 882,000 profit

AKSNES & BRATTLI SKOG OG MASKIN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AKSNES & BRATTLI SKOG OG MASKIN AS

Who owns AKSNES & BRATTLI SKOG OG MASKIN AS?

Gøran Kvåle Aksnes is the largest registered owner, with 50.0%.

What is the revenue of AKSNES & BRATTLI SKOG OG MASKIN AS?

AKSNES & BRATTLI SKOG OG MASKIN AS had revenue of NOK 10.9m in 2025.

Where is AKSNES & BRATTLI SKOG OG MASKIN AS based?

AKSNES & BRATTLI SKOG OG MASKIN AS has its business address in Tørvikbygd.

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.