BIZTRAC BETA
Computer consultancy and computer facilities management activities

TEF AS

Org. no. 931477021 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 647,000
Equity NOK −151,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−151k kr).
  • Nylig endring 2026-05-05 Adresseendring registrert 2026-05-05.

TEF AS is registered as a limited company in Bergen, Vestland with organisation number 931477021. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Programmeringstjenester. Konsulentvirksomhet tilknyttet informasjonsteknologi. Modellbyråvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 647,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 647,000
Equity
NOK −151,000
Est. value
NOK 5.8m

Financial health · 2025

Liquidity
0.83
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-19.9%
Weak
Equity as a share of total capital

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

Who owns TEF AS?

TOR EINAR FURRE
TEF AS
NOK 2.6m rev. · NOK 647,000 profit

TEF AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TEF AS

Who owns TEF AS?

TOR EINAR FURRE is the largest registered owner, with 100.0%.

What is the revenue of TEF AS?

TEF AS had revenue of NOK 2.6m in 2025.

Who is the general manager of TEF AS?

Tor Einar Furre is registered as general manager of TEF AS.

Where is TEF AS based?

TEF AS has its business address in Bergen.

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.