biztrac. BETA
COMPANY REGISTER PROFILE
914578795 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Floor and wall covering

EFOR AS

Org. no. 914578795 Limited company (AS) Namsos Incorporated 2014 Active
Revenue 2025 NOK 0
Operating profit NOK −21,000
Equity NOK 1.1m
Incorporated 2014
Share capital NOK 260,000

Signals

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

EFOR AS is registered as a limited company in Namsos, Trøndelag with organisation number 914578795. The business is classified under floor and wall covering (NACE 43.330). The company was incorporated in 2014. Registered share capital is NOK 260,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av aksjer og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −21,000
▼ −3 %
Equity
NOK 1.1m
▲ +88 %
Est. value
NOK 3.5m

Financial health · 2025

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

Who owns EFOR AS?

EFOR AS
NOK 0 rev. · NOK −21,000 profit

EFOR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EFOR AS own?

EFOR AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about EFOR AS

Who owns EFOR AS?

Bjørn Ingar Grunnan is the largest registered owner, with 100.0%.

What is the revenue of EFOR AS?

EFOR AS had revenue of NOK 0 in 2025.

Who is the general manager of EFOR AS?

Bjørn Ingar Grunnan is registered as general manager of EFOR AS.

Where is EFOR AS based?

EFOR AS has its business address in Namsos.

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.