BIZTRAC BETA
Operation of gravel and sand pits and mining of clay and kaolin

VISNES EKLOGITT AS

Org. no. 966794739 Limited company (AS) Hustadvika Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 28.5m
Operating profit NOK 2.1m
Equity NOK 14.2m
Incorporated 1993
Share capital NOK 100,000

VISNES EKLOGITT AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 966794739. The business is classified under operation of gravel and sand pits and mining of clay and kaolin (NACE 08.120). The company was incorporated in 1993. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive industriell virksomhet ved uttak og foredling av stein og mineralforekomster, samt det som naturlig står i forbindelse hermed, herunder deltagelse i andre foretak med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 28.5m in revenue and NOK 2.1m in operating profit.

Key figures · 2024

Revenue
NOK 28.5m
Operating profit
NOK 2.1m
Equity
NOK 14.2m
Est. value
NOK 14.0m

Financial health · 2024

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

Who owns VISNES EKLOGITT AS?

VISNES KALK OG MARMORBRUDD AS
VISNES EKLOGITT AS
NOK 28.5m rev. · NOK 2.1m profit

VISNES EKLOGITT AS has 1 registered shareholder:

All shareholders and roles →

Group structure

VISNES EKLOGITT AS er morselskap for 1 datterselskap:

Frequently asked questions about VISNES EKLOGITT AS

Who owns VISNES EKLOGITT AS?

VISNES KALK OG MARMORBRUDD AS is the largest registered owner, with 100.0%.

What is the revenue of VISNES EKLOGITT AS?

VISNES EKLOGITT AS had revenue of NOK 28.5m in 2024.

Where is VISNES EKLOGITT AS based?

VISNES EKLOGITT AS has its business address in Lyngstad.

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.