BIZTRAC BETA
COMPANY REGISTER PROFILE
975380564 ORG. NO. 2023 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Wholesale of other intermediate products

IDEFISK ANS

Org. no. 975380564 General partnership (ANS) Ås Incorporated 1995 Active
Ownership graph ↗
Revenue 2023 NOK 936,000
Equity NOK 508,000
Incorporated 1995

IDEFISK ANS is registered as a general partnership in Ås, Akershus with organisation number 975380564. The business is classified under wholesale of other intermediate products (NACE 46.860). The company was incorporated in 1995. The company's stated purpose is: “Selge varer, tjenester og å utvikle produkter for fiskeoppdrettsnæringen.”. The most recent filed accounts, for the 2023 financial year, show NOK 936,000 in revenue.

Key figures · 2023

Revenue
NOK 936,000
Equity
NOK 508,000
Est. value
NOK 546,000

Financial health · 2023

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

Who owns IDEFISK ANS?

No shareholders are registered for IDEFISK ANS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about IDEFISK ANS

What is the revenue of IDEFISK ANS?

IDEFISK ANS had revenue of NOK 936,000 in 2023.

Who is the general manager of IDEFISK ANS?

Svein Olav Fjæra is registered as general manager of IDEFISK ANS.

Where is IDEFISK ANS based?

IDEFISK ANS has its business address in Ås.

Property

Business address Soleglad Gamle Mossevei 5, 1433 Ås
Cadastral unit 3218-42/4/0/0
Building Tomannsbolig, horisontaldelt · 3 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.