BIZTRAC BETA
Rental and operating of own or leased real estate

BRENNA STASJON AS

Org. no. 916273053 Limited company (AS) Bamble Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 1.4m
Equity NOK 5.7m
Incorporated 2015
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BRENNA STASJON AS is registered as a limited company in Bamble, Telemark with organisation number 916273053. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 1.0m, divided into 100 shares. The company's stated purpose is: “Eie, utvikling, drift og utleie av fast eiendom, eie aksjer i andre selskap, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 1.4m
Equity
NOK 5.7m
Est. value
NOK 6.9m

Financial health · 2024

Liquidity
1.35
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
64.3%
Very good
Equity as a share of total capital

Who owns BRENNA STASJON AS?

BABORD AS
BRENNA STASJON AS
NOK 2.2m rev. · NOK 1.4m profit

BRENNA STASJON AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BRENNA STASJON AS er morselskap for 1 datterselskap:

Frequently asked questions about BRENNA STASJON AS

Who owns BRENNA STASJON AS?

BABORD AS is the largest registered owner, with 100.0%.

What is the revenue of BRENNA STASJON AS?

BRENNA STASJON AS had revenue of NOK 2.2m in 2024.

Where is BRENNA STASJON AS based?

BRENNA STASJON AS has its business address in Stathelle.

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.