BIZTRAC BETA
Construction of residential and non-residential buildings

TUSSEFARET 2 AS

Org. no. 925855650 Limited company (AS) Ullensaker Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −8,000
Equity NOK 1.0m
Incorporated 2020
Share capital NOK 600,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−8k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TUSSEFARET 2 AS is registered as a limited company in Ullensaker, Akershus with organisation number 925855650. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2020. Registered share capital is NOK 600,000, divided into 600000 shares. The company's stated purpose is: “Investering, eierskap, deltakelse, rådgiving i andre selskaper, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 1.0m
Est. value
NOK 1.0m

Financial health · 2024

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

Who owns TUSSEFARET 2 AS?

PORTNOR BYGG AS
TUSSEFARET 2 AS
NOK 0 rev. · NOK −8,000 profit

TUSSEFARET 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TUSSEFARET 2 AS

Who owns TUSSEFARET 2 AS?

PORTNOR BYGG AS is the largest registered owner, with 100.0%.

What is the revenue of TUSSEFARET 2 AS?

TUSSEFARET 2 AS had revenue of NOK 0 in 2024.

Where is TUSSEFARET 2 AS based?

TUSSEFARET 2 AS has its business address in Mogreina.

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.