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

FOSSENS EFTF AS

Org. no. 929208749 Limited company (AS) Indre Østfold Incorporated 1979 Active
Ownership graph ↗
Revenue 2025 NOK 23.2m
Operating profit NOK 325,000
Equity NOK 11.8m
Incorporated 1979
Employees 8
Share capital NOK 450,000

FOSSENS EFTF AS is registered as a limited company in Indre Østfold, Østfold with organisation number 929208749. 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 1979 and has 8 registered employees. Registered share capital is NOK 450,000, divided into 450 shares. The company's stated purpose is: “Transportvirksomhet og grustak, samt hva som står i forbindelse herved, herunder også å delta i andre selskaper, samt erverve faste eiendommer m.v.”. The most recent filed accounts, for the 2025 financial year, show NOK 23.2m in revenue and NOK 325,000 in operating profit.

Key figures · 2025

Revenue
NOK 23.2m
Operating profit
NOK 325,000
Equity
NOK 11.8m
Est. value
NOK 6.9m

Financial health · 2025

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

Who owns FOSSENS EFTF AS?

INGAR JENSEN AS
FOSSENS EFTF AS
NOK 23.2m rev. · NOK 325,000 profit

FOSSENS EFTF AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FOSSENS EFTF AS

Who owns FOSSENS EFTF AS?

INGAR JENSEN AS is the largest registered owner, with 33.3%.

What is the revenue of FOSSENS EFTF AS?

FOSSENS EFTF AS had revenue of NOK 23.2m in 2025.

Who is the general manager of FOSSENS EFTF AS?

Ingar Kasbo Jensen is registered as general manager of FOSSENS EFTF AS.

Where is FOSSENS EFTF AS based?

FOSSENS EFTF AS has its business address in Mysen.

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.