BIZTRAC BETA
Rental and operating of own or leased real estate

KLÆBU BT3 S3 AS

Org. no. 935342368 Limited company (AS) Grimstad Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK 20,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KLÆBU BT3 S3 AS is registered as a limited company in Grimstad, Agder with organisation number 935342368. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg, utvikling, utleie og drift av fast eiendom og hva som naturlig hører sammen med dette. Selskapet kan også opprette selskap og eie andeler i andre selskap.”.

Key figures · 2025

Operating profit
NOK −12,000
Equity
NOK 20,000
Est. value
NOK 19,000

Financial health · 2025

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

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

Who owns KLÆBU BT3 S3 AS?

LAGERSEKSJONER TRØNDELAG AS
KLÆBU BT3 S3 AS
· NOK −12,000 profit

KLÆBU BT3 S3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLÆBU BT3 S3 AS

Who owns KLÆBU BT3 S3 AS?

LAGERSEKSJONER TRØNDELAG AS is the largest registered owner, with 100.0%.

Who is the general manager of KLÆBU BT3 S3 AS?

Torjus Stalleland is registered as general manager of KLÆBU BT3 S3 AS.

Where is KLÆBU BT3 S3 AS based?

KLÆBU BT3 S3 AS has its business address in Grimstad.

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.