BIZTRAC BETA
Retail sale of clothing

SUBLINORGE AS

Org. no. 831163402 Limited company (AS) Giske Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −20,000
Equity NOK −257,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−257k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−20k kr).

SUBLINORGE AS is registered as a limited company in Giske, Møre og Romsdal with organisation number 831163402. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Salg av sublimeringsmaskiner og utstyr, kursvirksomhet og alt som hører naturlig til.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −20,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −20,000
Equity
NOK −257,000

Financial health · 2024

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

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

Who owns SUBLINORGE AS?

MARIANNE TRULSSEN NEDREGÅRD
SUBLINORGE AS
NOK 0 rev. · NOK −20,000 profit

SUBLINORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SUBLINORGE AS

Who owns SUBLINORGE AS?

MARIANNE TRULSSEN NEDREGÅRD is the largest registered owner, with 100.0%.

What is the revenue of SUBLINORGE AS?

SUBLINORGE AS had revenue of NOK 0 in 2024.

Who is the general manager of SUBLINORGE AS?

Marianne Trulssen Nedregård is registered as general manager of SUBLINORGE AS.

Where is SUBLINORGE AS based?

SUBLINORGE AS has its business address in Valderøya.

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.