biztrac. BETA
COMPANY REGISTER PROFILE
929405587 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of charities which distribute means themselves

LITTERATURBÅTEN EPOS STI

Org. no. 929405587 Foundation (STI) Kvam Incorporated 2022 Active
Revenue 2025 NOK 2.3m
Operating profit NOK −217,000
Equity NOK −399,000
Incorporated 2022
Employees 15
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−399k kr).

LITTERATURBÅTEN EPOS STI is registered as a foundation in Kvam, Vestland with organisation number 929405587. The business is classified under activities of charities which distribute means themselves (NACE 94.991). The company was incorporated in 2022 and has 15 registered employees. Registered share capital is NOK 100,000. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK −217,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
▼ −40 %
Operating profit
NOK −217,000
▼ −638 %
Equity
NOK −399,000
▼ −573 %

Financial health · 2025

Liquidity
0.80
Weak
Current assets ÷ current liabilities
Profitability
-4.5%
Not satisfactory
Return on total assets
Solidity
-9.7%
Weak
Equity as a share of total capital

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

Who owns LITTERATURBÅTEN EPOS STI?

No shareholders are registered for LITTERATURBÅTEN EPOS STI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LITTERATURBÅTEN EPOS STI

What is the revenue of LITTERATURBÅTEN EPOS STI?

LITTERATURBÅTEN EPOS STI had revenue of NOK 2.3m in 2025.

Who is the general manager of LITTERATURBÅTEN EPOS STI?

Maria Pile Svåsand is registered as general manager of LITTERATURBÅTEN EPOS STI.

Where is LITTERATURBÅTEN EPOS STI based?

LITTERATURBÅTEN EPOS STI has its business address in Strandebarm.

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.