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

ÅFJORDSAND AS

Org. no. 966110325 Limited company (AS) Åfjord Incorporated 1993 Active
Revenue 2025 NOK 6.4m
Operating profit NOK −496,000
Equity NOK 1.3m
Incorporated 1993
Share capital NOK 260,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−496k kr).

ÅFJORDSAND AS is registered as a limited company in Åfjord, Trøndelag with organisation number 966110325. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1993. Registered share capital is NOK 260,000, divided into 260 shares. The company's stated purpose is: “Grabbing, foredling, transport og omsetning av sand, samt befraktning. Selskapet kan engasjere seg i virksomhet som står i sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.4m in revenue and NOK −496,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.4m
▲ +2 %
Operating profit
NOK −496,000
▲ +37 %
Equity
NOK 1.3m
▼ −29 %
Est. value
NOK 2.8m

Financial health · 2025

Liquidity
1.74
Good
Current assets ÷ current liabilities
Profitability
-21.2%
Not satisfactory
Return on total assets
Solidity
61.7%
Very good
Equity as a share of total capital

Who owns ÅFJORDSAND AS?

ÅFJORDSAND AS
NOK 6.4m rev. · NOK −496,000 profit

ÅFJORDSAND AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ÅFJORDSAND AS

Who owns ÅFJORDSAND AS?

Stig Morten Gilde is the largest registered owner, with 76.9%.

What is the revenue of ÅFJORDSAND AS?

ÅFJORDSAND AS had revenue of NOK 6.4m in 2025.

Who is the general manager of ÅFJORDSAND AS?

Stig Morten Gilde is registered as general manager of ÅFJORDSAND AS.

Where is ÅFJORDSAND AS based?

ÅFJORDSAND AS has its business address in Åfjord.

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.