BIZTRAC BETA
Business and other management consultancy activities

TREASURY + FINANCE AS

Org. no. 822968562 Limited company (AS) Moss Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK −21,000
Equity NOK 586,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

TREASURY + FINANCE AS is registered as a limited company in Moss, Østfold with organisation number 822968562. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Rådgiving og håndtering innen finans og annet som naturlig faller sammen med dette .”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK −21,000
Equity
NOK 586,000
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns TREASURY + FINANCE AS?

JAN SCHIFFNER
TREASURY + FINANCE AS
NOK 1.4m rev. · NOK −21,000 profit

TREASURY + FINANCE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TREASURY + FINANCE AS

Who owns TREASURY + FINANCE AS?

JAN SCHIFFNER is the largest registered owner, with 100.0%.

What is the revenue of TREASURY + FINANCE AS?

TREASURY + FINANCE AS had revenue of NOK 1.4m in 2025.

Who is the general manager of TREASURY + FINANCE AS?

Jan Schiffner is registered as general manager of TREASURY + FINANCE AS.

Where is TREASURY + FINANCE AS based?

TREASURY + FINANCE AS has its business address in Moss.

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.