BIZTRAC BETA
COMPANY REGISTER PROFILE
981658892 ORG. NO. 2023 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 02.09.2026
FRIFUGL ANS is registered as “In liquidation” with the Brønnøysund Register Centre.
Computer programming activities

FRIFUGL ANS

Org. no. 981658892 General partnership (ANS) Nordre Follo Incorporated 2000 In liquidation
Ownership graph ↗
Revenue 2023 NOK 258,000
Operating profit NOK 1
Equity NOK 0
Incorporated 2000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

FRIFUGL ANS is registered as a general partnership in Nordre Follo, Akershus with organisation number 981658892. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2000. The company's stated purpose is: “Utviklingsselskap som utformer tilrettelagte, teknologiske løsninger for bedrifter og organisasjoner i Norge. Selskapet tilbyr tjenester knyttet til audiovisuell utforming og teknisk utvikling av internettløsninger. For kunder tilbys også drift og supportavtaler for utviklede løsninger.”. The most recent filed accounts, for the 2023 financial year, show NOK 258,000 in revenue and NOK 1 in operating profit.

Key figures · 2023

Revenue
NOK 258,000
Operating profit
NOK 1
Equity
NOK 0

Financial health · 2023

Liquidity
1.00
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FRIFUGL ANS?

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

Frequently asked questions about FRIFUGL ANS

What is the revenue of FRIFUGL ANS?

FRIFUGL ANS had revenue of NOK 258,000 in 2023.

Where is FRIFUGL ANS based?

FRIFUGL ANS has its business address in Ski.

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.