BIZTRAC BETA
COMPANY REGISTER PROFILE
924917172 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

TBAED INVEST AS

Org. no. 924917172 Limited company (AS) Lillestrøm Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 48,000
Operating profit NOK 17,000
Equity NOK 87,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-02-25 Adresseendring registrert 2026-02-25.

TBAED INVEST AS is registered as a limited company in Lillestrøm, Akershus with organisation number 924917172. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Formål er å eie aksjer og andeler i andre selskaper, samt hva dermed står i forbindelse. Samt bistå andre selskap med rådgiving innen økonomisk og administrativt arbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 48,000 in revenue and NOK 17,000 in operating profit.

Key figures · 2025

Revenue
NOK 48,000
Operating profit
NOK 17,000
Equity
NOK 87,000
Est. value
NOK 108,000

Financial health · 2025

Liquidity
10.08
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
90.1%
Weak
Equity as a share of total capital

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

Who owns TBAED INVEST AS?

TOMMY BAKKE EDVARTSEN
TBAED INVEST AS
NOK 48,000 rev. · NOK 17,000 profit

TBAED INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TBAED INVEST AS

Who owns TBAED INVEST AS?

TOMMY BAKKE EDVARTSEN is the largest registered owner, with 100.0%.

What is the revenue of TBAED INVEST AS?

TBAED INVEST AS had revenue of NOK 48,000 in 2025.

Where is TBAED INVEST AS based?

TBAED INVEST AS has its business address in Kjeller.

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.