BIZTRAC BETA
Uoppgitt

FRISINGER INVEST AS

Org. no. 889111852 Limited company (AS) Gjøvik Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 75,000
Operating profit NOK 15,000
Equity NOK −537,000
Incorporated 2005
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−537k kr).
  • Nylig endring 2026-02-23 Adresseendring registrert 2026-02-23.

FRISINGER INVEST AS is registered as a limited company in Gjøvik, Innlandet with organisation number 889111852. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Selskapets formål er å eie og forvalte aksjer og andre verdipapirer, samt deltagelse i andre selskaper med samme eller lignende formål. ”. The most recent filed accounts, for the 2024 financial year, show NOK 75,000 in revenue and NOK 15,000 in operating profit.

Key figures · 2024

Revenue
NOK 75,000
Operating profit
NOK 15,000
Equity
NOK −537,000
Est. value
NOK 77,000

Financial health · 2024

Liquidity
29.44
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-150.1%
Weak
Equity as a share of total capital

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

Who owns FRISINGER INVEST AS?

HANS ANDERS URBAN FRISINGER
FRISINGER INVEST AS
NOK 75,000 rev. · NOK 15,000 profit

FRISINGER INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRISINGER INVEST AS

Who owns FRISINGER INVEST AS?

HANS ANDERS URBAN FRISINGER is the largest registered owner, with 100.0%.

What is the revenue of FRISINGER INVEST AS?

FRISINGER INVEST AS had revenue of NOK 75,000 in 2024.

Where is FRISINGER INVEST AS based?

FRISINGER INVEST AS has its business address in Gjøvik.

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.