biztrac. BETA
COMPANY REGISTER PROFILE
935583675 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Retail sale of clothing

SUBTEKST AS

Org. no. 935583675 Limited company (AS) Bergen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 25,000
Operating profit NOK −6,000
Equity NOK 17,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

SUBTEKST AS is registered as a limited company in Bergen, Vestland with organisation number 935583675. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Nettbasert salg av tekst- og innholdsdrevne produkter som klær, trykksaker og publikasjoner.”. The most recent filed accounts, for the 2025 financial year, show NOK 25,000 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 25,000
Operating profit
NOK −6,000
Equity
NOK 17,000
Est. value
NOK 16,000

Financial health · 2025

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

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

Who owns SUBTEKST AS?

SUBTEKST AS
NOK 25,000 rev. · NOK −6,000 profit

SUBTEKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SUBTEKST AS

Who owns SUBTEKST AS?

Christine Hille Alvøen is the largest registered owner, with 100.0%.

What is the revenue of SUBTEKST AS?

SUBTEKST AS had revenue of NOK 25,000 in 2025.

Who is the general manager of SUBTEKST AS?

Christine Hille Alvøen is registered as general manager of SUBTEKST AS.

Where is SUBTEKST AS based?

SUBTEKST AS has its business address in Mathopen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.