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

AKSVIK FJELLSPRENGING AS

Org. no. 936133649 Limited company (AS) Vinje Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 356,000
Equity NOK 415,000
Incorporated 2025
Share capital NOK 140,000

AKSVIK FJELLSPRENGING AS is registered as a limited company in Vinje, Telemark with organisation number 936133649. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2025. Registered share capital is NOK 140,000, divided into 100 shares. The company's stated purpose is: “Fjellsprenging og der tilhørende tjenester, samt salg av varer i tilknytning til disse tjenestene.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 356,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 356,000
Equity
NOK 415,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns AKSVIK FJELLSPRENGING AS?

AKSVIK FJELLSPRENGING AS
NOK 1.3m rev. · NOK 356,000 profit

AKSVIK FJELLSPRENGING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AKSVIK FJELLSPRENGING AS

Who owns AKSVIK FJELLSPRENGING AS?

Marius Aksvik is the largest registered owner, with 90.0%.

What is the revenue of AKSVIK FJELLSPRENGING AS?

AKSVIK FJELLSPRENGING AS had revenue of NOK 1.3m in 2025.

Who is the general manager of AKSVIK FJELLSPRENGING AS?

Marius Aksvik is registered as general manager of AKSVIK FJELLSPRENGING AS.

Where is AKSVIK FJELLSPRENGING AS based?

AKSVIK FJELLSPRENGING AS has its business address in Rauland.

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.