biztrac. BETA
COMPANY REGISTER PROFILE
994260537 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Accounting and bookkeeping

TRYGG-ØKONOMI AS

Org. no. 994260537 Limited company (AS) Tromsø Incorporated 2013 Active
Revenue 2025 NOK 6.3m
Operating profit NOK 662,000
Equity NOK 3.0m
Incorporated 2013
Employees 7
Share capital NOK 30,000

TRYGG-ØKONOMI AS is registered as a limited company in Tromsø, Troms with organisation number 994260537. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2013 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Regnskapstjenester, økonomisk rådgivning, samt øvrige tjenester som naturlig faller inn herunder. Selskapet skal også kunne delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.3m in revenue and NOK 662,000 in operating profit.

Former names: FO REGNSKAP AS

Key figures · 2025

Revenue
NOK 6.3m
▲ +10 %
Operating profit
NOK 662,000
▼ −42 %
Equity
NOK 3.0m
▲ +27 %
Est. value
NOK 5.7m

Financial health · 2025

Liquidity
5.10
Very good
Current assets ÷ current liabilities
Profitability
22.6%
Very good
Return on total assets
Solidity
81.3%
Very good
Equity as a share of total capital

Who owns TRYGG-ØKONOMI AS?

TRYGG-ØKONOMI AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRYGG-ØKONOMI AS

Who owns TRYGG-ØKONOMI AS?

Frank Odin Landbakk Johansen is the largest registered owner, with 56.7%.

What is the revenue of TRYGG-ØKONOMI AS?

TRYGG-ØKONOMI AS had revenue of NOK 6.3m in 2025.

Who is the general manager of TRYGG-ØKONOMI AS?

Frank Odin Landbakk Johansen is registered as general manager of TRYGG-ØKONOMI AS.

Where is TRYGG-ØKONOMI AS based?

TRYGG-ØKONOMI AS has its business address in Tromsdalen.

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.