BIZTRAC BETA
Manufacture of other textiles n.e.c.

SEFAR AS

Org. no. 914778565 Limited company (AS) Stad Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 82,000
Operating profit NOK 64
Equity NOK 119,000
Incorporated 2014
Share capital NOK 30,000

SEFAR AS is registered as a limited company in Stad, Vestland with organisation number 914778565. The business is classified under manufacture of other textiles n.e.c. (NACE 13.990). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Produksjon av tekstiler i ull og i andre naturfibre til videresalg. Formidling av lokal kultur, utleie av leilighet(er) til turisme/korttidsleie, samt rådgivning primært tilknyttet digitale utfordringer.”. The most recent filed accounts, for the 2024 financial year, show NOK 82,000 in revenue and NOK 64 in operating profit.

Key figures · 2024

Revenue
NOK 82,000
Operating profit
NOK 64
Equity
NOK 119,000
Est. value
NOK 63,000

Financial health · 2024

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

Who owns SEFAR AS?

INGER METTE ELISABETH SEFLAND
SEFAR AS
NOK 82,000 rev. · NOK 64 profit

SEFAR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SEFAR AS own?

SEFAR AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SEFAR AS

Who owns SEFAR AS?

INGER METTE ELISABETH SEFLAND is the largest registered owner, with 100.0%.

What is the revenue of SEFAR AS?

SEFAR AS had revenue of NOK 82,000 in 2024.

Who is the general manager of SEFAR AS?

Inger Mette Elisabeth Sefland is registered as general manager of SEFAR AS.

Where is SEFAR AS based?

SEFAR AS has its business address in Nordfjordeid.

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.