biztrac. BETA
COMPANY REGISTER PROFILE
927434075 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Sports and recreation education

STALL T AS

Org. no. 927434075 Limited company (AS) Larvik Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK −60,000
Equity NOK 127,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

STALL T AS is registered as a limited company in Larvik, Vestfold with organisation number 927434075. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drift av rideskole og salg av tjenester innenfor hestesport samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK −60,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
▼ −48 %
Operating profit
NOK −60,000
▼ −128 %
Equity
NOK 127,000
▼ −36 %
Est. value
NOK 300,000

Financial health · 2025

Liquidity
1.43
Satisfactory
Current assets ÷ current liabilities
Profitability
-4.7%
Not satisfactory
Return on total assets
Solidity
11.3%
Satisfactory
Equity as a share of total capital

Who owns STALL T AS?

STALL T AS
NOK 2.7m rev. · NOK −60,000 profit

STALL T AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STALL T AS

Who owns STALL T AS?

Terje Olsen-Nalum is the largest registered owner, with 100.0%.

What is the revenue of STALL T AS?

STALL T AS had revenue of NOK 2.7m in 2025.

Who is the general manager of STALL T AS?

Terje Olsen-Nalum is registered as general manager of STALL T AS.

Where is STALL T AS based?

STALL T AS has its business address in Stavern.

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.