BIZTRAC BETA
Development of building projects

FISCUS INVEST AS

Org. no. 912039358 Limited company (AS) Hamar Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −30,000
Equity NOK 3.4m
Incorporated 2013
Share capital NOK 30,000

Signals

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

FISCUS INVEST AS is registered as a limited company in Hamar, Innlandet with organisation number 912039358. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i andre selskaper, samt drive med eiendomsutvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −30,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −30,000
Equity
NOK 3.4m
Est. value
NOK 3.5m

Financial health · 2024

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

Who owns FISCUS INVEST AS?

JARLE NÆSSET
FISCUS INVEST AS
NOK 0 rev. · NOK −30,000 profit

FISCUS INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FISCUS INVEST AS own?

FISCUS INVEST AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about FISCUS INVEST AS

Who owns FISCUS INVEST AS?

JARLE NÆSSET is the largest registered owner, with 100.0%.

What is the revenue of FISCUS INVEST AS?

FISCUS INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of FISCUS INVEST AS?

Jarle Næsset is registered as general manager of FISCUS INVEST AS.

Where is FISCUS INVEST AS based?

FISCUS INVEST AS has its business address in Hamar.

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.