BIZTRAC BETA
Public relations and communication activities

TEKSTUELL AS

Org. no. 928286460 Limited company (AS) Nesodden Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 105,000
Operating profit NOK 177
Equity NOK 46,000
Incorporated 2021
Share capital NOK 30,000

TEKSTUELL AS is registered as a limited company in Nesodden, Akershus with organisation number 928286460. The business is classified under public relations and communication activities (NACE 73.300). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tekstforfatting, tekstproduksjon, og konsulentvirksomhet innen design, merkevarebygging, teknologi og digitale tjenester, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 105,000 in revenue and NOK 177 in operating profit.

Key figures · 2024

Revenue
NOK 105,000
Operating profit
NOK 177
Equity
NOK 46,000
Est. value
NOK 23,000

Financial health · 2024

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

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

Who owns TEKSTUELL AS?

KARINA RAUNHOLM
TEKSTUELL AS
NOK 105,000 rev. · NOK 177 profit

TEKSTUELL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TEKSTUELL AS

Who owns TEKSTUELL AS?

KARINA RAUNHOLM is the largest registered owner, with 100.0%.

What is the revenue of TEKSTUELL AS?

TEKSTUELL AS had revenue of NOK 105,000 in 2024.

Who is the general manager of TEKSTUELL AS?

Karina Raunholm is registered as general manager of TEKSTUELL AS.

Where is TEKSTUELL AS based?

TEKSTUELL AS has its business address in Fagerstrand.

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.